Skip to main content
Codeg ingests and displays conversation history from all your local agents. Every session is parsed directly from disk and presented in a structured, searchable interface — no cloud sync required.

​
How it works

When you open a folder or click Import, Codeg scans the local filesystem paths for each supported agent and reads their session files. Sessions are deduplicated, parsed into a common format, and stored in a local SQLite database for fast retrieval. Nothing leaves your machine. Each conversation captures:
  • Agent type — which agent ran the session (Claude Code, Codex CLI, OpenCode, Gemini CLI, OpenClaw, or Cline)
  • Message turns — every user message and agent response in order
  • Tool calls — each tool the agent invoked, with inputs, outputs, and status
  • Git branch — the branch that was active when the session started
  • Model — the model used, if reported by the agent
  • Usage stats — token counts, context window usage, and session duration where available

​
Browsing conversations

The sidebar groups sessions by folder (project directory). Each folder entry shows:
  • The folder name and path
  • A count of total conversations
  • Which agent types have sessions in that folder
Click a folder to expand it and see its conversation list. Conversations are sorted newest-first by default. Each item in the list shows the title (or a generated preview), the agent type, message count, and start time.

​
Conversation detail

Click any conversation to open the full session view. The detail panel shows:
  • Message turns — rendered with full Markdown support, code highlighting, and collapsible tool call blocks
  • Tool calls — each call shows the tool name, status, raw input, and raw output
  • Usage stats — total tokens, context window percentage used, and session duration
  • Git branch — the branch recorded at session start
  • Model — the model identifier if the agent reported it

​
Searching and filtering

Use the search bar at the top of the conversation list to filter by:
  • Conversation title
  • Folder name or path
  • Git branch name
  • Model name
You can also filter by agent type to narrow results to a single agent, and sort by newest, oldest, or most messages.

​
Stats

The sidebar footer shows aggregate stats across all imported sessions:
  • Total conversations
  • Total messages
  • Breakdown by agent type, sorted by conversation count

​
Importing conversations

Click the Import button in the folder toolbar to sync new sessions from disk. Codeg scans the agent data directories, imports any conversations not already in the local database, and returns a count of imported and skipped records.
Import runs automatically when you first open a folder. Use the manual Import button to pick up sessions added after the folder was opened.

​
Conversation status

Conversations have a status field that reflects their lifecycle:
StatusMeaning
activeAn agent session is currently running for this conversation
completedThe session ended normally
You can update the title of any conversation directly from the detail view.

​
Local-first storage

All conversation data is stored in a local SQLite database under ~/.local/share/codeg/ (or CODEG_DATA_DIR if set). Parsing happens on your machine. No conversation content is sent to any external server.