---
title: "Supported coding agents"
description: "Which coding agents antiburn can read sessions from, where it looks on each platform, and where support is partial."
url: "https://antiburn.ai/docs/agents/supported-agents/"
---
## What "supported" means

antiburn never talks to a coding agent directly — it reads the session files an agent has already written to disk and builds its analysis from that. There's nothing to configure per agent; a supported agent's sessions show up once antiburn has scanned the machine. What varies by agent is which platforms it's read on natively, whether it's also read inside WSL (Windows Subsystem for Linux), and, for two agents, whether antiburn can reach their live in-memory state at all.

## The matrix

| Agent          | Where antiburn looks                                                                                                                                     | Platforms                            | WSL                                                     |
| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------ | ------------------------------------------------------- |
| Claude Code    | `~/.claude/projects/<encoded-path>/*.jsonl`, plus session manifests under the platform config directory                                                  | macOS, Windows, Linux                | Supported                                               |
| Codex          | `~/.codex/sessions/YYYY/MM/DD/*.jsonl` (or `$CODEX_HOME`)                                                                                                | macOS, Windows, Linux                | Supported                                               |
| OpenCode       | `opencode.db` (read-only), falling back to `storage/session`, `storage/message`, `storage/part` JSON                                                     | macOS, Windows, Linux                | Supported (via the OpenCode CLI, not the live database) |
| Cursor         | Legacy `chatSessions/*.json`, `~/.cursor/projects/*/agent-transcripts/**`, and desktop composer state (`workspaceStorage` / `globalStorage/state.vscdb`) | macOS, Windows, Linux                | Not supported                                           |
| GitHub Copilot | VS Code chat sessions under `workspaceStorage/*/chatSessions/*.json`, and the Copilot CLI/Desktop App's `session-state/<id>/events.jsonl`                | macOS, Windows, Linux                | Not supported                                           |
| Cline          | `~/.cline/**` (CLI and JetBrains mirror) and the VS Code extension's `globalStorage`                                                                     | macOS, Windows, Linux                | Not supported                                           |
| Kiro           | `<Kiro app config>/User/globalStorage/kiro.kiroagent/workspace-sessions/**/<id>.json` and `*.chat` files                                                 | macOS, Windows, Linux                | Not supported                                           |
| Amp            | `~/.local/share/amp/threads/*.json` (`%APPDATA%\amp\threads\` on Windows), falling back to `~/.amp/file-changes/**`                                      | macOS, Windows, Linux                | Not supported                                           |
| Pi             | `~/.pi/agent/sessions/` (or `$PI_AGENT_DIR`)                                                                                                             | macOS, Linux only                    | Not supported                                           |
| Antigravity    | `$GEMINI_HOME` (default `~/.gemini`) native session databases and brain transcripts, plus older workspace-storage JSON                                   | macOS, Windows, Linux, **disk-only** | Not supported                                           |
| Windsurf       | VS Code-style `workspaceStorage/*/chatSessions/*.json`, **disk-only**                                                                                    | macOS, Windows, Linux                | Not supported                                           |

**Disk-only** means antiburn reads the files the agent's process happens to have written, not a live API the editor exposes. A conversation that exists only in that editor's memory and hasn't been flushed to one of those files won't appear yet.

## Notes per agent

**Claude Code.** antiburn also watches the session manifests the Claude desktop app writes under the platform's config directory, because those can move a session's recency forward even when the transcript file itself hasn't changed. Claude Code is antiburn's fallback agent — a session in Claude's transcript format that doesn't match a more specific parser is still read as Claude Code. Sub-agent work (Workflows and Task-tool sub-agents) is read from a `subagents/` folder alongside the parent transcript, so orchestrated sessions are visible too.

**Codex.** The session tree is flat rather than scoped by repository — everything lives under one date-based hierarchy, or under `$CODEX_HOME` when that's set.

**OpenCode.** antiburn prefers a read-only connection to OpenCode's own `opencode.db` and falls back to the older per-record JSON fragments when no database is present. It gets the same depth of session analysis and Insights coverage as Claude Code and Codex. Under WSL, antiburn never opens that live database over the Windows-to-WSL network path — it asks the distro's own OpenCode CLI for the data instead.

**Cursor.** Several generations of local storage have accumulated, and antiburn reads all of them: legacy chat sessions, JSONL agent transcripts, and desktop composer state split across `workspaceStorage` and a SQLite database.

**GitHub Copilot.** Two independent stores both surface as Copilot: VS Code's own chat-session files, and the separate Copilot CLI / Copilot Desktop App session-state directory, which writes each session's transcript as `events.jsonl` (honoring `XDG_CONFIG_HOME` when set).

**Cline.** Cline 2.0 and later writes a metadata file and a separate messages file per task; antiburn reads only the metadata file, so a task isn't indexed twice.

**Kiro.** Only Kiro's IDE session store is read today. A Kiro CLI session layout exists but isn't documented well enough yet for antiburn to parse.

**Amp.** antiburn reads the primary threads directory first, and only falls back to the older file-changes tree when no threads are found there.

**Pi.** antiburn reads Pi v3 CLI transcripts only. Pi has no live plan-limit meter of its own, but does get dedicated session analysis and Insights coverage, the same as Claude Code, Codex, and OpenCode.

**Antigravity.** Never the live language-server APIs the editor exposes — a session that exists only in memory won't appear until Antigravity writes it out. Three related identities share this support (Antigravity CLI, Antigravity IDE, and the legacy single-binary layout), each under its own subdirectory of `$GEMINI_HOME`. Quota percentages and reset times for the providers behind Antigravity come from the separate live plan-usage integration, not the session database.

**Windsurf.** Disk-only in the same way as Antigravity: only the documented local chat-session files are read, never Windsurf's running process.

Supported coding agents

Which coding agents antiburn can read sessions from, where it looks on each platform, and where support is partial.