Agents
Imported history
The chats you had in Claude Code, Codex, Cursor, Muse Code and OpenCode sync into Codz’s projects and sidebar, ready to read and to pick up where they left off.
Codz lists the chats your agents keep on this Mac next to the chats you run in Codz. It reads them from each provider’s own files, so a chat you start in the ChatGPT app’s Codex or in the Claude Code CLI appears in the sidebar within seconds, and you can open it, read it and continue it.
The provider’s files stay the record. Codz keeps no copy of an imported transcript: it reads the provider’s file when you open the chat. Hiding an imported chat, or deleting Codz’s own history, leaves the provider’s transcript where it was, and a chat the provider deletes (Claude Code removes sessions older than 30 days unless you change cleanupPeriodDays) leaves Codz too.
Which chats sync
Every chat in a folder that’s in your project list or sidebar syncs from every provider, however old:
- A project’s folders, and the folders inside them. Add an existing folder to a project and all of its chats come in; create a project in Codz and the chats you start there in Claude Code, Codex, Cursor, Muse Code or OpenCode appear in it as they begin.
- A folder you show from the sidebar’s Hidden folders.
- A folder where you run a chat in Codz, or continue an imported one.
Elsewhere, Codz lists the newest chats from each provider so that their folders appear under Hidden folders, ready to show. Folders that only hold imported chats stay hidden until you add them.
Where imported chats come from
| Provider | Codz reads | Left out |
|---|---|---|
| Claude Code | The session files in ~/.claude/projects | Subagent transcripts, and sessions whose folder no longer exists |
| Codex (ChatGPT) | Codex’s thread index in ~/.codex | Subagent threads |
| Cursor | Cursor’s own database in ~/Library/Application Support/Cursor/User/globalStorage | Subagent chats, unsent drafts, and chats whose folder no longer exists |
| Muse Code | Muse’s session index in ~/.local/share/muse | Reminder and subagent sessions, and sessions whose folder no longer exists |
| OpenCode | ~/.local/share/opencode/opencode.db | Subagent sessions, and sessions whose folder no longer exists |
A chat that Codz itself ran on a provider isn’t listed a second time. A Claude Code session that ran in a worktree of its own is listed under the repository it belongs to.
Archived chats
A chat you archived in Claude Desktop, Codex, Cursor or OpenCode is filed in Codz’s Archive rather than the sidebar. Find it under Settings ▸ History ▸ Archived chats, where Restore brings it back to the sidebar. A restore holds until you archive or unarchive the chat in its own app again.
Imported chats sit in the sidebar with your other chats and follow the same arrangement. When the sidebar is sorted by Last updated, a chat you keep working on in the provider’s own app moves up as it is updated.
Read an imported chat
Select an imported chat to load its transcript from the provider’s files. Reading needs neither the provider’s CLI nor a sign-in. Codz shows the most recent 180 messages of the chat.
While the chat is open, Codz keeps following the provider’s record of it: a turn running in the provider’s own app appears in the transcript as it happens.
Continue an imported chat
Type in the composer and send, as in any chat. Codz resumes the same conversation with the provider’s CLI, so the provider’s own history stays one thread. Sending needs that CLI installed and signed in; Providers & logins covers setup.
- Check the mode before you send. Cursor and OpenCode chats open in Ask. A Codex chat opens in Ask if it ran read-only, and a Claude Code chat opens in Plan if it began in plan mode; otherwise they open in Full access.
- No Undo in imported chats. Turns you run here get no workspace checkpoint, so their change cards can’t undo. See Reviewing changes.
- It becomes a Codz chat when you change its engine. Changing an imported chat’s provider, model, mode or approval level turns it into a regular Codz chat, which you archive and delete like any other.
Hide an imported chat
Right-click an imported chat in the sidebar and choose Hide (with several selected, Hide N chats). Imported chats offer Hide where Codz chats offer Archive. Codz removes the row and remembers the chat, so the next sync doesn’t bring it back. The provider’s transcript is not touched, and the chat is still there in the provider’s own app. A chat you delete in Codz stays deleted too, including one Codz ran.
Sync automatically or by hand
Codz watches each provider’s files and picks up new chats and changes as they are written, within a few seconds. Every 10 minutes while a Codz window is open it also syncs everything once more, which catches chats deleted or archived in their app.
Each provider has its own controls under Settings ▸ History ▸ Chats from other apps:
| Control | What it does |
|---|---|
| Sync automatically | On by default. Turn it off and Codz leaves that provider’s chats as they are until you sync by hand, though a chat whose transcript the provider deleted still leaves. |
| Sync now | Syncs that provider at once, whether or not it syncs automatically. |
| Sync all now | Syncs every provider at once. Also in the command palette (⌘K) as Sync Chats from Other Apps. |
Each row says how many of the provider’s chats Codz lists, and when it last synced if you sync it by hand. If Codz can’t read a provider’s files, the row says so and the chats Codz already listed stay as they were.
From a terminal, codz sessions sources shows the same, and codz sessions sync syncs every provider (--provider claude, codex, cursor, muse or opencode for one).
Your Codz chats in Claude Desktop
To see the Claude chats you start in Codz in Claude Desktop’s sidebar too, turn on Settings ▸ Models & providers ▸ Claude ▸ Show chats in Claude Desktop. It is off by default.
With it on, a Claude chat you started in Codz is added to Claude Desktop’s sidebar when one of its turns finishes. Claude Desktop comes to the front and switches to the chat as it is added. Each chat is added once; if Claude Desktop is closed, the chat is added the next time it opens. Side chats, imported chats and chats on an additional Claude login are not added.
To show one chat in another app once, use Open in in the chat’s options menu; see Handoffs & side chats.
Export and delete
| To | Use |
|---|---|
| Save one chat as Markdown | Export transcript… in the chat’s options menu (… in the header). The file is named after the chat and has a Prompt and a Response heading per turn, with reasoning, tool calls, their output and file changes. |
| Copy one chat as Markdown | Chat ▸ Copy Conversation (⌘⇧C) |
| Save all of Codz’s chats | Export local task history under Settings ▸ Data & refresh, a private JSON file of Codz task transcripts and metadata |
| Restore or delete archived chats | Settings ▸ History, where each archived chat has Restore and Delete… |
| Delete all of Codz’s chats | Delete local task history under Settings ▸ Data & refresh |
Delete local task history can’t be undone. It removes Codz’s records of your chats and their checkpoints. Provider-owned transcripts and synced usage totals are not deleted, isolated checkouts are kept under Settings ▸ History for separate cleanup, and imported chats are hidden so they don’t reappear.
Troubleshooting
A chat I had in Claude Code, Codex, Cursor, Muse Code or OpenCode isn’t listed. Check the table above: subagent chats are left out, as are chats whose folder has been moved or deleted. An archived chat is under Settings ▸ History ▸ Archived chats. An older chat in a folder that isn’t a project or in the sidebar isn’t listed: add the folder to a project, or show it from Hidden folders. A chat you hid or deleted stays gone. If the provider syncs by hand, click its Sync now under Settings ▸ History ▸ Chats from other apps.
An imported chat opens with “Nothing to show from this transcript”. Codz found no messages it can show in the provider’s file. The chat can still be continued: send a message.
I can read a chat but can’t send. Sending needs the provider’s CLI installed and signed in. Troubleshooting covers provider setup errors.