Skip to main content
If you’ve been using Claude Code, Codex, or Cursor before installing IronBee, your past sessions live on disk but aren’t in the Console yet. ironbee import backfills them into the IronBee Collector so your analytics include history, not just sessions from today forward. Discovery scans all three stores (~/.claude/projects/, ~/.codex/sessions/, and Cursor’s local state.vscdb) and routes each session through the right importer automatically, with no client flag needed. Sessions already tracked are skipped automatically, so the command is safe to re-run.

Basic usage

From a project directory, import that project’s history:
ironbee import
By default this reads the current project’s Claude Code, Codex, and Cursor sessions and ships any that aren’t already in the Collector.
Cursor has no per-session transcript file — its “transcript” is the composer stored in state.vscdb. Token and cost figures for imported Cursor sessions come from Cursor’s usage API and require cursor.apiAccess to be on (the default); without it, imported Cursor sessions carry structure only.

Choosing what to import

Pick at most one scope (the default is the current directory):
FlagScope
(none)The current project directory
--projects <p1,p2,...>Specific projects by absolute path, comma-separated
--all-projectsEvery project Claude Code, Codex, or Cursor has tracked on this machine
--transcript <path>A single .jsonl transcript file (Claude Code / Codex)

Limiting the time range

Pick at most one (the default is no time filter):
FlagRange
--since <duration>Relative window — 30d, 2w, 6m, 12h
--from <date> [--to <date>]Explicit window; --to defaults to now
ironbee import --since 30d
ironbee import --from 2026-01-01 --to 2026-03-31

Preview and safety

FlagDescription
--dry-runPrint a cost/event summary and exit without sending anything
--yesSkip the confirmation prompt (for scripts/CI)
--forceRe-import sessions that are already tracked
--concurrency <N>Parallel sessions to process (default 4, range 1–32)
Always start with a dry run if you’re unsure of the volume:
ironbee import --since 30d --dry-run

Common scenarios

GoalCommand
Onboard the current project, last 30 daysironbee import --since 30d
Full history for the current projectironbee import
Everything on this machine, last 6 monthsironbee import --all-projects --since 6m
A quarter across all projectsironbee import --all-projects --from 2026-01-01 --to 2026-03-31
Preview before committingironbee import --since 30d --dry-run
Scripted, no promptironbee import --since 60d --yes

What’s next?

Inspecting sessions

Check verdicts and session state from the terminal.

Open the Console

Your imported sessions appear alongside live ones, with the same analytics and timelines.