Connect your tools

Seggo does two separate things with your tools:

• It reads their history. Seggo imports each tool’s own history from your computer, read-only, so you can search it and continue it elsewhere. This needs no setup and changes nothing in the tool.
• It connects to them, if you turn a tool on. A connected tool can save handoffs, read project context, and use the task board. This is the part that changes a tool’s settings, and only after you see a preview and confirm.

Which tools work

Tool	History Seggo reads	Can be turned on
Claude Code	Yes	Yes
Codex	Yes	Yes
Cursor	Yes (editor chats). Cursor Agent CLI chats are detected but not read yet.	Yes
Gemini CLI	Yes (some older installs: your prompts only)	Yes
Antigravity	Yes, when its text transcripts exist	Yes
Claude Desktop	No history is read. Handoffs it saves arrive directly.	Yes
Claude Cowork	Not supported yet. Use the Markdown import.	No
ChatGPT, Claude.ai, Markdown	From exported files you choose	No (imports only)

Seggo never writes to a tool’s own folders (~/.claude, ~/.codex, ~/.gemini, ~/.cursor, or Cursor’s app data folder) while reading history. There’s no catch-all scraper: if Seggo can’t read a format reliably, it says “detected, not yet supported” instead of guessing.

Turning a tool on

Each tool has one On/Off switch under Tools in Seggo.

1. Switch the tool On.
2. Choose the projects it can use. Seggo lists the folders the tool has worked in, newest first, and ticks the five most recent. You can add any other folder by its path.
3. Read the preview. Show exact changes shows the exact lines Seggo will add. Nothing is changed until you click Confirm.

Turning a tool on does all of these, or none of them:

1. Adds Seggo to the tool’s own MCP settings file, so the tool can call Seggo’s tools (such as saving a handoff).
2. Adds a marked Seggo section to each chosen project’s rules file (for example CLAUDE.md or AGENTS.md), asking the tool to read context and save handoffs.
3. For Claude Code, adds a session-end hook to each chosen project’s .claude/settings.local.json.
4. Limits the tool to the projects you chose. It can’t read or write Seggo data for other projects.

Each tool’s page lists its exact settings file and rules file.

Note

The rules section is a request to the tool’s model, not a guarantee. A tool may sometimes skip it. Once the tool is on, you can also ask directly: “Save a Seggo handoff for this work.”

You can do the same from a terminal. The first command previews, the second applies exactly that preview:

seggo connect codex --project /path/to/your-project
seggo connect codex --project /path/to/your-project --apply TOKEN

Turning a tool off and Undo

Switch the tool Off. It shows its own preview of what it will remove.

• A file you haven’t touched since is put back exactly as it was.
• A file you’ve changed since keeps your newer work and loses only Seggo’s part.
• If you edited Seggo’s part by hand, Off stops and changes nothing until that’s fixed.
• If you added a seggo entry to a tool yourself, the switch leaves it alone, both on and off.
• If any file can’t be written, every file already changed is put back.

Every change is also listed under What Seggo changed, each with Undo. From a terminal: seggo disconnect codex, then the --apply command it prints.

To change which projects a tool can use, turn it off and on again.

What the Tools page shows

Each tool card answers four questions:

Status	Means
Found	The tool’s folder exists on this computer.
Readable	Seggo has imported history from it.
Has read context	The tool has read shared project context through Seggo at least once.
Saving handoffs	The tool’s newest handoff came through complete.

Other labels you may see: Not found, Not imported yet, Not supported yet, Not checked yet and Could not confirm. None of these statuses means a live connection.

Known limits

• Tools change where and how they store things without notice. Seggo keeps unknown records instead of dropping them, but a new format may need a Seggo update.
• We’ve confirmed Claude Code’s settings file. For the other tools, we haven’t confirmed every settings file yet. If a tool doesn’t see Seggo, tell us at contact@bozomalabs.com. Turning a tool off still removes what Seggo added.
• Secret masking is on by default and best-effort, not perfect.