Use Bwat
Manage sessions
Pause a task, return later, or move it between VS Code and the terminal without starting the investigation again.
On this page
Sessions belong to a project
Each conversation is saved locally and associated with the workspace where it began. Bwat uses that association to put the most relevant work first when you open history or continue from the terminal.
VS Code and the CLI share local sessions on the same machine. A conversation started in the editor can be continued in the terminal, and CLI turns appear when you reopen it in VS Code.
Resume in VS Code
Open the Bwat view in the Activity Bar to see recent sessions for the current workspace. Search by title, select a conversation, and continue where you stopped. Inside an open panel, run /history to open the same history view.
Resume in the CLI
| Command | What it does |
|---|---|
bwat --continue or bwat -c | Resume the most recent conversation related to the current folder |
bwat --resume or bwat -r | Open a searchable picker of earlier conversations |
bwat --resume <id> | Resume a known conversation directly |
/history | Open the session picker without leaving an interactive run |
cd /path/to/your/project bwat --continue
Start fresh without losing history
Run /clear to begin a new conversation. The earlier session stays in history; clear does not delete its transcript. Start a new session when the goal changes substantially or the old discussion is steering the agent toward assumptions that no longer apply.
Keep a long session useful
Bwat automatically condenses older conversation when a long task needs more room. You can also run /compact at a natural boundary, such as after investigation and before implementation.
/compact Keep the accepted API contract, unresolved test failure, and the files already changed.
- Use one session for one durable goal.
- Correct a wrong assumption as soon as you notice it.
- Ask Bwat to summarize the current state before a long break.
- Put stable project rules in
BWAT.mdinstead of repeating them in every session.
Where sessions live
Machine sessions are stored under ~/.bwat/sessions/. They can contain prompts, code excerpts, command output, and tool results, so treat the directory as private. Bwat removes obvious credential patterns before writing transcripts, but that is a safety net rather than a reason to paste secrets into chat.