Sessions
A session is one conversation with the AI. It has a name, a provider, a model and a session mode. Sessions belong to the exploration and stay after the app is closed.
Sessions are stored in .codeexplorer/sessions/ of the exploration. That
folder is not shared through Git: sessions are private, large and contain
absolute paths. Results that others need go into projectdocs or specs.
Start a session
- Click + in the chat header, or
- choose AI › New Chat (
Cmd+Shift+N, Windows/Linux:Ctrl+Shift+N), or - send
/clear. The new session keeps model and mode.
A new session gets the name "Chat" and the time, for example "Chat 22:23:25".
With Check git status before new chat on (AI Settings › General), Tracemoor checks the project first. If there are uncommitted changes, a dialog asks: Start New Chat starts the chat anyway, Commit First opens the Git view. The commit message field then holds the name of the previous session.
To start a session with another provider, choose the provider in the provider list of the chat header.
Switch, rename, delete
| Action | Control |
|---|---|
| Switch | Session list in the chat header |
| Rename | Pencil in the chat header, double-click the session name, or AI › Rename Session… |
| Delete | Bin in the chat header |
| Reload | Circular arrows in the chat header. Reads the session again from the transcript of claude. Claude (CLI) only. |
Save a conversation as a projectdocs entry
- Open the dashboard with the phase list.
- Drag the handle at the left of the line below the chat header onto a phase. To place the conversation under an entry, drop it on the entry.
Tracemoor writes the whole conversation as an entry of type chatlog into
the phase. The title is the session name.
To save a single answer, drag the message onto a phase or an entry. The new entry contains that message. See projectdocs dashboard.
A conversation is rarely what others need. A summary of the result, anchored to the code it is about, is easier to find later. Ask the AI to write it as a projectdocs entry and to set the anchors. See projectdocs and the AI.
Export a session
- Select the session in the chat header.
- Choose File › Export AI Session….
- Choose the file name and click Save.
The active session is written as a Markdown file. Without an active session the chat shows "No active AI session to export.". The export is a copy for reading or archiving. It cannot be imported again.
Continue in a new session
A long session fills the context window. The CTX bar in the chat header shows how full it is. Answers get slower and less precise when it is nearly full. Continue in a new session with a handover:
- Ask the AI to write the current state into a projectdocs entry: what is done, the next step, open questions, the last commit.
- Start the new session from that entry:
- right-click the entry in the dashboard and choose New Chat from this, or
- open the entry and choose AI › New Chat from Current Entry.
The new session starts with the entry as context. In Brave mode the AI can
start the new session itself with session_new_chat_from_entry and pass a
first message. See Longer tasks.
/compact is the alternative inside the same session: it replaces the
conversation with a summary of it. The summary is not stored as an entry.
Hand work to someone else
Sessions are not shared. A teammate continues from the shared result:
- Ask the AI to write the result as a projectdocs entry or a spec and commit the exploration.
- The teammate pulls the exploration and starts a new session from the entry.
Both sessions then work from the same written state. See Sharing an exploration.