Get session ingest status
Report coding-session ingestion progress for the caller: how many session nodes and edges exist, how much is still queued, which warm layers (identity, manifold, domains, insights, temporal) have.
building is true. Warm-layer reads degrade to false rather than failing, so a partially migrated org still gets a usable answer.
Authorization
This route requires thewrite scope.
A missing or invalid credential returns 401 authentication_error. A valid credential without the scope returns 403 permission_denied, and the problem body names the exact scope required.
Headers
These are request conventions the contract does not declare as parameters, so they do not appear in the schema tables below.Success responses
Errors
application/problem+json body carrying a stable code, a requestId, and a suggestedAction where Exo has one. See Errors.
Notes
- Poll
building, notwarmLayers. The layers are data-dependent: an organization with no dated content never grows temporal phases, so waiting for all of them to turn true polls forever.
Authorizations
An Exo API key (exo_...) sent as the X-Exo-API-Key header.
Response
Session counts, queue depth and warm-layer readiness.
GET /v1/ingest/session-status: Claude Code ingestion + warm-layer progress.
Backs the frontend "Connect Claude Code" status panel: how many session nodes/edges have landed, when the last line arrived, whether jobs are still draining/building, and which warm layers exist yet.
Which cold-start warm layers have materialized for the user/org.