Concepts

Supported agents

Which coding-agent histories ctx can discover, import, and search locally.

ctx support means native local-history import. The CLI can discover or read a provider's persisted local history, import supported records into SQLite, and return cited search results from that index.

Support does not mean ctx launches the agent, installs the agent, changes the agent's files, or normalizes every provider-specific field into the same output shape.

Current support

This table is a format-support summary. Use Provider history support for the default local paths and ctx sources --json for the state of your machine.

Agent history	Support status	Notes
Codex	Supported	Session transcripts and prompt history can be discovered and imported when present locally.
Pi	Supported	Local JSONL session history can be imported when the supported file exists.
Claude Code	Supported	Project transcript history can be imported from local Claude Code data.
OpenCode	Supported	Local OpenCode database history can be imported.
Antigravity / Gemini CLI	Supported	Local Antigravity and Gemini CLI history can be imported when present.
Cursor	Supported	Local Cursor agent transcript history can be imported.
Copilot CLI	Supported	Local Copilot CLI session-state history can be imported.
Factory AI Droid	Supported	Local Factory AI Droid sessions can be imported.

The table describes provider formats ctx currently knows how to read. It does not guarantee that a given machine has those histories available.

Verify on your machine

Run:

ctx sources
ctx sources --json

The JSON form is the clearest way to check support and availability:

{
  "provider": "codex",
  "native_import": true,
  "importable": true,
  "status": "available"
}

Read those fields separately:

native_import: true means ctx has parser support for that provider format;
importable: true means the local path exists and has supported data available to import;
status explains the current source state, such as available, empty, missing, unknown, or unsupported.

A provider can have native_import: true and importable: false. That usually means the agent has not written local history on this machine, the expected path is empty, or ctx needs an explicit import path.

Import supported history

The installer runs ctx setup by default. You can also import directly:

ctx setup
ctx import --all
ctx import --provider codex
ctx import --provider pi
ctx import --provider claude
ctx import --provider opencode
ctx import --provider antigravity
ctx import --provider gemini
ctx import --provider cursor
ctx import --provider copilot-cli
ctx import --provider factory-ai-droid

Use --path when the provider history lives outside the location ctx normally checks:

ctx import --provider opencode --path ~/.local/share/opencode/opencode.db

Search after import

ctx search "failed migration" --provider codex
ctx search "database retry" --provider opencode
ctx show event <ctx-event-id> --window 3
ctx show session <ctx-session-id> --mode lite

Search uses the local SQLite index. --refresh auto is the default search mode and can refresh discovered Codex session sources before querying. For other providers, run ctx import --provider <provider> or ctx import --all when you need the latest local history in the index.

What varies by provider

Providers keep different kinds of local records. Some histories include fine-grained events with tool calls and outputs. Others expose less structure or store different metadata. ctx normalizes enough to search, show, locate, and export sessions, but the exact fields in a result can vary by source.

When exact behavior matters, inspect the local source record:

ctx search "the phrase" --provider <provider> --json
ctx locate event <ctx-event-id>
ctx export session <ctx-session-id> --mode full --format markdown