# groundedby > The reference on AI coding agent session data: where Claude Code, Codex, Cursor and others keep your history, how to read it, and what it is worth. groundedby (a SecOne Inc. product) documents where AI coding agents store session history, how to read and manage it, and what it is worth. Its browser evaluator counts sessions locally; nothing is uploaded. An opt-in marketplace for licensing redacted sessions is in development; there is a waitlist. ## Agents - [Where Claude Code stores your session history](https://groundedby.com/agents/claude-code.md): Claude Code keeps every session as a JSONL file in ~/.claude/projects and deletes them after 30 days by default. How to find, resume, export, keep and delete them. - [Where OpenAI Codex CLI stores your session history](https://groundedby.com/agents/codex.md): Codex CLI saves each session as a rollout JSONL file in ~/.codex/sessions by date and compresses old ones to .jsonl.zst. How to find, resume, archive and delete them. - [Where Cursor stores your chat and agent history](https://groundedby.com/agents/cursor.md): Cursor keeps agent and chat history in a SQLite database, state.vscdb. Where it is on macOS, Windows and Linux, how to read a copy, and how to clear it. - [Where Gemini CLI stores your session history](https://groundedby.com/agents/gemini-cli.md): Gemini CLI saves sessions as JSONL files in ~/.gemini/tmp//chats and deletes them after 30 days by default. How to find, resume, share and keep them. - [Where GitHub Copilot CLI stores your session history](https://groundedby.com/agents/github-copilot-cli.md): Copilot CLI keeps sessions in ~/.copilot/session-state and syncs them to your GitHub account by default. Where they are, how to export them and how to stop the sync. - [Where OpenCode stores your session history](https://groundedby.com/agents/opencode.md): OpenCode keeps every session in one SQLite database, opencode.db, under ~/.local/share/opencode. How to find it, list, export, share and delete sessions. - [Where Cline stores your task history](https://groundedby.com/agents/cline.md): Cline v4 and the Cline CLI keep sessions in ~/.cline/data, with older tasks in VS Code's globalStorage. Where each lives, and how to resume, export and delete them. - [Where Aider stores your chat history](https://groundedby.com/agents/aider.md): Aider writes chat history as Markdown in .aider.chat.history.md at the root of each git repo. Where it is, what is in it, and how to restore or clear it. - [Where Goose stores your session history](https://groundedby.com/agents/goose.md): Goose keeps sessions in a SQLite database, sessions.db, under ~/.local/share/goose. How to find it on each system, export sessions and import other agents' history. - [Where Zed stores agent panel threads](https://groundedby.com/agents/zed.md): Zed keeps agent panel threads in a SQLite database, threads.db, as zstd-compressed JSON. Where it is on macOS, Linux and Windows, and how to archive or delete threads. - [Where Amp stores your threads](https://groundedby.com/agents/amp.md): Amp, Sourcegraph's coding agent, stores every thread on its servers with a URL, not on your disk. How to list, search, export and delete Amp threads. - [Where Kiro CLI stores your chat sessions](https://groundedby.com/agents/kiro.md): Kiro CLI, formerly Amazon Q Developer CLI, keeps sessions in a local SQLite database and session files. What is documented, and how to resume, save and delete sessions. - [Where Continue stored your chat sessions](https://groundedby.com/agents/continue.md): Continue is no longer maintained, and its sessions remain as JSON files in ~/.continue/sessions. Where to find them and how to export them before you move on. - [Where Roo Code stored your task history](https://groundedby.com/agents/roo-code.md): Roo Code was discontinued in May 2026. Its task history is JSON in VS Code's globalStorage under RooVeterinaryInc.roo-cline. Where to find it and how to export it. ## Guides - [How to evaluate your AI agent sessions](https://groundedby.com/guides/how-to-evaluate-your-agent-sessions.md): A step-by-step way to measure your Claude Code and Codex history - how many sessions, how much real work, which products - and estimate what it is worth. - [What makes an AI agent session valuable](https://groundedby.com/guides/what-makes-a-session-valuable.md): Buyers of agent session data want long sessions of real work with tools, errors and recoveries. Here is what raises a session's value and what makes it worthless. - [Who buys AI agent session data](https://groundedby.com/guides/who-buys-agent-session-data.md): The buyers of AI coding agent sessions - AI labs, data vendors and developer-tool companies - what each wants, and what they have paid in 2025 and 2026. - [Can you sell your AI coding sessions?](https://groundedby.com/guides/can-you-sell-your-ai-coding-sessions.md): Ownership, employer rights, personal data and AI providers' terms - the questions to answer before you license a Claude Code or Codex session to anyone. - [How to redact secrets and personal data from agent logs](https://groundedby.com/guides/redact-secrets-from-agent-logs.md): AI agent session files capture API keys, tokens, emails and customer data. How to find them in Claude Code and Codex logs, and how to mask them before sharing. - [Tools that read your agent session logs - ccusage and alternatives](https://groundedby.com/guides/tools-that-read-agent-session-logs.md): ccusage, claude-code-log, claude-code-viewer, Agent Sessions, splitrail and tokscale compared - what each does with your Claude Code and Codex logs, and what it reads. - [What is inside an AI agent session file](https://groundedby.com/guides/whats-inside-an-agent-session-file.md): A field-by-field look at Claude Code and Codex session files - records, messages, tool calls, results and token usage - and what each reveals about how the work went. - [Claude Code vs Codex CLI session logs](https://groundedby.com/guides/claude-code-vs-codex-session-logs.md): How Claude Code and Codex CLI differ in where they store sessions, file format, retention, compression, resume commands and training defaults - side by side. ## Docs - [What is groundedby](https://groundedby.com/docs/what-is-groundedby.md): groundedby is a reference on AI coding agent session data, a browser evaluator, and a waitlist for an opt-in marketplace for redacted sessions. - [How the evaluator works](https://groundedby.com/docs/how-the-evaluator-works.md): The groundedby evaluator reads Claude Code and Codex session files in your browser and counts sessions, turns, tool calls and active hours. Nothing is uploaded. - [Privacy model](https://groundedby.com/docs/privacy-model.md): How groundedby handles your data - the evaluator runs locally, the waitlist stores only what its form shows, and future sales happen one reviewed session at a time. - [Valuation method](https://groundedby.com/docs/valuation-method.md): How the groundedby evaluator estimates what your agent sessions are worth - session tiers, the prices buyers have paid, and what the range does not mean. - [The waitlist and the marketplace](https://groundedby.com/docs/waitlist-and-marketplace.md): What happens after you join the groundedby waitlist, how the opt-in marketplace for agent sessions will work for sellers and buyers, and what we will check. ## Blog - [$500, then $200: what one posting tells us about the price of a coding session](https://groundedby.com/blog/mercor-500-then-200-coding-session-price.md): In October 2026 Mercor paid developers $500 per recorded coding session, then cut it to $200 within a week. What the price says about the market for agent session data. ## Optional - [Evaluator](https://groundedby.com/evaluate): count your Claude Code and Codex sessions in the browser - [Full text](https://groundedby.com/llms-full.txt): every article in one file