Coincide Get Coincide

Guide

Import sessions from Claude Code and Codex

Conversations you started with claude or codex in Terminal don’t have to stay there. Coincide can import them as threads that keep the agent’s own session, so the next message continues where the CLI left off.

Updated

Importing a session

  1. Choose File › Import CLI Session…. Coincide scans your local histories: ~/.claude/projects for Claude Code and ~/.codex/sessions and ~/.codex/archived_sessions for Codex. It follows CLAUDE_CONFIG_DIR and CODEX_HOME when Coincide itself was started with them, for example from Terminal; otherwise use Choose File… for histories kept elsewhere.
  2. Search by title or folder and select a session to preview the conversation.
  3. Click Import. If you already imported that session, Coincide offers Open Existing Thread instead of making a duplicate.

To import a file the list doesn’t show, use Choose File… and pick a Claude Code session or Codex rollout .jsonl file.

What you get

The original file

Coincide never changes the CLI’s file. It keeps an exact private copy in its own data folder; File › Reveal Imported Source shows that copy in Finder. Anything the transcript can’t show stays in that copy: unsupported records, attachments, excluded branches of the conversation and text beyond the limits below. Deleting the imported thread also deletes its copy, and Undo restores both.

Limits

LimitValue
File size32 MB per file
Record size4 MB per record
Records100,000 per file
Text shown per transcript field100,000 characters
Preview200,000 characters
Sessions listed2,000, newest first

A session over the file limits shows “This session exceeds the import limits (32 MB per file, 4 MB per record, or 100,000 records).” When some histories can’t be listed, the window says so and suggests Choose File….

Good to know