Skip to main content

Providers

Import the seven supported providers

Supported input formats and safe import expectations for ChatGPT, Claude, Gemini, Claude Code, Codex, Gemini CLI, and Cursor.

By Novus Stream Solutions Editorial Team. Last reviewed Thu Aug 20 2026 00:00:00 GMT+0000 (Coordinated Universal Time).

ChatGPT, Claude, and Gemini

  • ChatGPT accepts the official account export ZIP or conversations.json. Only the branch ending at the conversation's current node is counted, so regenerations and edits are not counted twice.
  • Claude accepts the official account export ZIP or supported JSON. Current exports spell out every assistant content block, which is where tool calls and AI active time come from; an older export carrying message text only leaves both unavailable rather than reporting zero.
  • Gemini accepts a Google Takeout ZIP containing supported Gemini Apps or My Activity records. Only Prompted activity rows count as prompts — Canvas creations and "Used Gemini Apps" rows are side effects of one. Gemini's answers are recoverable from the MyActivity.html form and are absent from the JSON activity form.

Official ZIPs may contain images, audio, and other attachments. The importer skips those entries before decompression and reads only supported statistics files. Browser safety ceilings allow up to 10,000 selected files, 1 GiB of selected input, and 2 GiB of supported expanded data; these are archive and memory safeguards, not account quotas.

Coding tools

  • Claude Code accepts supported JSONL sessions and telemetry.
  • Codex CLI and Desktop accept supported rollout JSONL and preserve the product surface as a statistic.
  • Gemini CLI accepts local OpenTelemetry JSONL. Disable prompt logging before collecting telemetry.
  • Cursor accepts exported Markdown and user-selected SQLite snapshots with recognized schema signatures. A Markdown transcript labels its tool and command turns, so an absence there is a real zero; a workspace snapshot reports tool calls only when its rows spell each turn out as content parts, and leaves the count unavailable when they do not.

Select the transcript files these tools write as they run — one JSON object per line — or a ZIP of them. A summary, report, or spreadsheet describing that usage is rejected even when its numbers are correct: every statistic here is derived from the underlying events, so totals computed elsewhere have no events to verify and are never adopted as if they had been.

Current Codex rollouts contribute embedded session identity, completed-turn duration, cumulative token usage, tool calls, launched sub-agents, models, and anonymous repository grouping when those fields are present. Repeated snapshot files for one embedded session are collapsed to the newest complete snapshot.

Fail-closed behaviour

Choose the provider explicitly. Shape detection is only assistance. Unknown Cursor databases, missing timestamps, corrupt records, nested archives, and unsupported schemas are rejected or reported as partial warnings. They never become synthetic sessions.

Was this page helpful?

Your answer stays in this browser. It is not sent anywhere, and no account or cookie is involved.