Conversation History
Every message you send and every response the agent produces is saved automatically. Settings → History lets you browse, search, and review past conversations.
Opening History
Section titled “Opening History”- Open settings (gear icon on projects home, or ⋯ More options → Settings).
- Switch to General scope if a project is selected.
- Select History from the sidebar.
For a quick jump to recent conversations without opening the full history page, use ⋯ More options → History in the chat header.
Browsing Conversations
Section titled “Browsing Conversations”The history view shows conversations across all projects and branches, with the most recent at the top. Each entry shows thread name, project name, timestamp, and a preview of the initial message.
Click any conversation to expand it and view the full message history, including tool calls and agent responses.
Optional columns include tokens, model, branch, and more — toggle them in the column visibility controls.
Filtering
Section titled “Filtering”Use the filter controls to narrow down conversations by project or branch.
Token Usage
Section titled “Token Usage”Each conversation entry can show token usage and the model used. This helps track API costs and understand which conversations were the most expensive.
Relationship to New Chat
Section titled “Relationship to New Chat”Starting New Chat in a branch creates a new conversation ID but does not delete the previous one. All conversations are preserved in history.
Export for Review
Section titled “Export for Review”Dump a thread or conversation as JSONL for offline review:
cd cli && bun run dump:conversation -- --thread <threadId> [--conversation <conversationId>] [--out export.jsonl]While Tarsk is running, the same payload is available from:
GET /api/conversations/:threadId/exportGET /api/conversations/:threadId/:conversationId/export
Data Retention
Section titled “Data Retention”Conversation history is stored in the local SQLite database (tarsk.db). It is never sent to external servers. Deleting a branch removes all associated conversation data.
- Use History to find solutions from earlier sessions
- Start a New Chat for each logical step to keep conversations focused
- Review token usage to understand which models and tasks consume the most tokens