Skip to Content
ConnectorsClaude Code sessions

Claude Code sessions — claude_code

Ingests Claude Code session transcripts into the data plane — one event per message, keyed by session, with project, branch, and model as labels and token-usage fields. Sub-agents roll up into the same source. Your agent sessions become a queryable source like any other: correlate what the agent did with what your systems did, and let the agent read back its own history.

Sessions are fed by the NavFlow plugin for Claude Code — it ships each session’s transcript to the daemon over HTTP as the session progresses. This works the same against a local or remote daemon, and the one install also wires up MCP read-back.

Set up

The console has a one-click page — Sources → Add source → claude_code — that shows the install command wired to your instance’s URL (and token, if it needs one). Or run it directly in Claude Code:

/plugin marketplace add glassflow/navflow /plugin install navflow@navflow

The install prompts for:

  • NavFlow URL — the daemon’s base URL (the default http://127.0.0.1:8787 matches navflow up; use your instance’s URL otherwise)
  • Access token (optional) — only on a secured instance; prefer a read + ingest API key so the plugin can both stream sessions and read back over MCP. Stored in the OS keychain.
  • Stream this session into NavFlow — the capture toggle (on by default)

That’s the only step. One install wires both directions:

  • Capture — hooks ship new transcript lines to /ingest/claude_code on each prompt, tool use, and session end. The plugin creates the push source on the daemon the first time it runs — no manual source setup.
  • Read-back — the plugin registers the navflow MCP server, so the same agent can query the data plane.

Capture is forward-only — sessions stream from when the plugin is installed onward; existing transcripts already on disk aren’t backfilled.

Configuration

The push source is created automatically by the plugin; these fields tune what’s stored:

fieldtypedescription
redactboolredact obvious secrets/tokens before storing (default true)
include_thinkingboolinclude assistant thinking blocks in the rendered text (default false)

Redaction runs server-side in the connector, so it applies before anything is stored.

Provided labels

session (the key), project, branch, model, type (message type), sidechain (sub-agent messages).

Verify

Start a Claude Code session and do some work. In the console, Explore lists sessions under the session key; the source’s Recent events shows messages as they ship. With the plugin installed, you can also just ask:

Use navflow to show me my current session’s timeline.

Last updated on