Supported is a functional product claim. For a provider's normal supported
version, the public CLI automatically locates an ordinary default native
history source, imports it through ctx import --all, and makes meaningful
user and assistant content available through search, show, and citations.
Repeating an unchanged import is a stable no-op without source failures or
duplicate records, and the route participates in the shared incremental,
read-only history architecture. Public deterministic tests exercise that
contract for every supported provider. Deeper route qualification is separate
from this functional support claim.
Support means backfilling history that the provider persists during ordinary operation. Output from an installed runtime hook, opt-in exporter, or separately configured sink does not qualify as provider history support.
The provider import policy in
provider-import-policy.md defines the native
storage families and the rules for real conversation text, tool output, raw
diffs, oversized rows, and fixtures.
Machine-readable provider metadata lives in
provider-support-matrix.json. Its
tool_output and command_output fidelity flags describe complete normalized
result bodies where the provider exposes them, subject only to the explicit
record-size and content policies. The public source formats below identify
discovery/import source shapes; stored event metadata may use the corresponding
per-file adapter format, such as
codex_session_jsonl for files discovered under codex_session_jsonl_tree.
Each row's configured_root object also records whether persistent named roots
are enabled and, when enabled, the required file or directory kind and the
provider's expansion strategy. intentional_automatic_exact means the provider
retains automatic
discovery plus one-shot exact import but does not accept ctx sources add.
Each provider row also has lineage_support. session_relationship is either
exact_relationship or unknown. event_origin distinguishes exact_copy,
certified_prefix, explicit_no_copy, and unknown. These values describe
what the shipped adapter admits into Core, not every feature the upstream tool
may expose. unknown does not mean unique, and similar transcript text never
upgrades it. A provider remains unknown until its adapter emits the typed
contract from stable structural data.
Custom History has a separate opt-in described in
custom-history-import-format.md. A durable
provider_native_v1 source can state an exact relationship and exact copied
event selectors. Legacy files, unstable IDs, command-only plugins, and generic
ordered-prefix claims remain unknown.
General history support does not imply exact MCP activity attribution. That
event-local Core capability has its own provider + route + source format +
format version authority in
mcp-tool-call-attribution-capabilities.json.
Capability revision 4 exact providers are Codex, Warp, and Copilot CLI. The
complete evidence matrix contains 48 base routes and 52 capability lanes:
three exact, 48 not-qualified, and one excluded. The Deep Agents hosted trace
is excluded from the local-only boundary, while its local SQLite history import
remains Supported but not qualified for exact attribution. See
mcp-tool-call-attribution.md for absence,
privacy, migration, and retrieval semantics.
Current provider activity capture retains invocation/result channels at native
event granularity for the qualified tuples; it does not change general provider
support or the exact-attribution qualification counts.
See mcp-exchange-capture.md.
The public support matrix is:
Codex session-tree discovery and exact --path import accept both ordinary
.jsonl rollouts and official standard-Zstandard .jsonl.zst rollouts. Both
representations derive source, session, and event identity from the embedded
Codex session UUID. If both representations of one native session coexist,
ctx selects raw JSONL first (then lexical path order) and publishes one logical
source; removing either representation does not change logical IDs.
Hermes Agent uses the native hermes_state_sqlite route. On Linux, a non-root
ctx process with the certified read-only live-WAL path makes new sessions and
appended records converge on native-watch and search refreshes. Where that fast
path is unavailable, incremental refresh defers without copying the provider
database. Structural edits, deletions, and deferred increments reconcile in
roughly 60–80 minutes with a healthy daemon, or on
ctx import --provider hermes or ctx import --all.
Factory AI Droid history is discovered automatically at ~/.factory/sessions.
An exact path remains available, for example
ctx import --provider factory-ai-droid --path /path/to/factory/sessions.
Grok Build history is discovered at absolute $GROK_HOME/sessions when the
override is set, or ~/.grok/sessions otherwise. Each admitted session
directory requires authoritative updates.jsonl; derived session sidecars
are not import authority. Exact updates.jsonl files can be selected with
ctx import --provider grok-build --path /path/to/updates.jsonl.
DeepSeek Harness is Supported for exact local format version 0 only. The
automatic winner is absolute $DSH_HOME/sessions for a nonempty
absolute override, otherwise ~/.dsh/sessions; empty or whitespace-only
values are unset, while relative overrides require an explicit --path.
Default persistence uses nested */*/session.jsonl.zstd, and configured raw
persistence uses nested */*/session.jsonl. Exact leaves can be selected with
ctx import --provider deepseek-harness --path /path/to/session.jsonl.zstd.
Other format versions and layouts are unsupported, hosted/cloud history is out
of scope, and this import does not qualify exact MCP server/tool attribution.
Unknown required events and future format versions fail the source. Delegated
sessions remain independently searchable, but their immediate parent header
does not prove the transitive root identity required for typed lineage edges.
fx supports fx v0.0.10 schema-v4 session manifests with schema-v1/v2
conversation events, legacy marker-less schema-v1/v2 snapshots, and schema-v3
transactional event logs. The default root is ~/.fx/sessions; named and exact
imports accept the same sessions-tree layout. Ordinary root cache files are ignored.
For conversation logs, ctx retains messages, tool calls and complete retained
result text, reasoning text, interruption and completed-turn metadata, and
context summaries. Results come from tool-results; command output comes from
logs/commands, including framed stdout/stderr replay. Missing, unsafe, binary
text results, and oversized content have explicit capture states; previews are
never represented as complete results. Individual artifacts are bounded at
8 MiB, replay metadata at 65,536 frames, and aggregate Core content at 16 MiB.
Opaque model-resume signatures and encrypted replay fields are omitted.
Artifact changes or late repair replay the whole session; unchanged artifacts
permit ordinary log append. This favors complete refresh over append performance
for sessions that frequently add artifacts. Native session and sequence identities
remain stable through artifact repair. Literal child-owner parent metadata is
retained without inferring transitive ancestry.
Schema-v3 logs still require authority.json and a matching
commit.<generation>.json watermark. Pending commits and uncommitted tails are
excluded; their session.json is only a projection. Legacy snapshots are limited
to 16 MiB. A supported legacy snapshot and its schema-v3 migration retain their
existing stable identities. Conversation migration retains the native session,
but uses the conversation log's event identities. Marker-less schema-v3 snapshots,
future schemas, hosted history, and exact MCP server/tool attribution are unsupported.
Devin is Supported through the native devin_cli_sessions_sqlite route
reading ~/.local/share/devin/cli/sessions.db. The route is named for the CLI
because Devin keeps per-surface state under a shared devin/ data root, so a
store written by another Devin surface would be a separate route rather than
this one. Admission is structural rather than version-pinned: every table,
column, and index the importer reads is probed, so a migration that removes or
reshapes them is refused, while one that only adds keeps importing. The
migration version feeds the capability digest, so any change to it rotates the
published content digest and forces a full re-scan. Each session stores its
messages as a forest, so the imported transcript is the walk from
sessions.main_chain_id up parent_node_id, reversed, with pre-compaction
history spliced in wherever a chain node records metadata.summarized_from.
System prompts sit on that chain and are imported as notices; the node a
compaction wrote is imported as a summary. Nodes off the chain are counted but
not imported: summarizer threads, abandoned regenerated turns, and the
pre-compaction copies Devin rewrote. Subagent threads become separate delegated
sessions when Devin records either a foreground subagent/chain_node_id
back-link or a durable subagent_heads chain tip, so foreground and durable
background subagents are imported. Foreground links inside a subagent also
retain nested children and identify their immediate parent. Durable heads
identify the root session; an immediate parent is claimed only when foreground
links identify one unambiguous caller. Persistent subagent history is retained
across compaction when the continuation reaches the same agent's earlier
history, including when the summary points before its previous tip. A subagent
tree without either exact tip link remains unclaimed. Native assistant messages
with visible text retain
generation metadata when Devin writes it; tool-only and empty-content events do
not retain that payload. Session-level model, agent mode, cost, and token data
are not projected as Core facts. Exact MCP server/tool attribution is not
supported.
ctx sources --format json reports each known provider source with import_support
and importable fields. A source is importable only when provider-specific
transcript files exist and match the documented format. NanoClaw participates in
native automatic import from an exact project CWD or official launchd/systemd
service registration; exact --path imports remain available for unregistered
project roots.
Local checks exercise supported imports, provider filtering, citations, and deterministic search without executing provider CLIs, reading real user history, requiring API keys, or making network calls.