Claude Code and Codex sessions

Claude Code and Codex save the history of every session on your computer. MindDuck can read that history and add each session to memory as an ordinary chat: you can find it with search, open it on your phone and ask the assistant about it. What you decided and discussed with an agent stays with you after the agent deletes its history, and after you move to another agent.

MindDuck only reads the history files. It does not run the agents, does not sign in to your Anthropic or OpenAI accounts and changes nothing in their folders. No model is needed for the import, and nothing leaves the device.

The import needs you to be signed in under Settings → Account with active access to MindDuck. See Account.

Turn the import on

1. Open Settings → Agents.
2. Turn on the switch for Claude Code, for Codex, or for both.
3. In Sessions to import, choose how far back to go:
   • Only sessions from now on - only those that start or continue after you turn the import on;
   • The last 30 days and everything new - also the sessions of the last 30 days;
   • Every saved session - everything the agent keeps on this computer.

There is nothing else to do. While MindDuck is open and the workspace is unlocked, new messages appear in the chat a few seconds after the agent finishes its answer.

A long history is imported in the background and gives way to everything else: you can keep using the app. The line under the list of agents shows how many sessions are still waiting.

If an agent is not installed, it says Not found on this computer. You can turn its switch on in advance: the import starts when the agent saves its first session.

What goes into the chat

• Your prompts, including those you sent while the agent was working.
• The agent's answers: its remarks in order. Work with tools is folded into one line, for example Ran 3 commands · edited src/main.rs.

Left out: command output and the content of files the agent read, the model's reasoning, sessions of helper agents, the agent's own service messages.

Images from your prompts are not imported; a note like [1 image attached] stays in their place. A very long message, such as a pasted log of hundreds of kilobytes, is kept at its beginning, with a note saying how much was left out.

The chat has the same name as the session has in the agent. Without a name, the first line of the first prompt names it. In the list the chat is marked with its source: Imported from Claude Code or Imported from Codex.

Keys and passwords

Before saving, MindDuck removes from the text whatever looks like a credential: API keys of known services, tokens, private keys, passwords in addresses like postgres://user:password@host, values of variables like API_KEY=…. [secret removed] is left in their place.

The filter recognises a shape, not a meaning. It will not notice a password typed as an ordinary word in a sentence. If a session had something that does not belong in memory, delete the message or the chat in the usual way, see Chat and message actions.

Project

A new chat is filed under a project automatically:

• if the session was started in a folder linked to one project in Settings → Folders, the chat goes to that project. Folders inside it count too;
• otherwise the chat goes to the project chosen in Project for sessions;
• if that says No project, the chat stays without a project.

The project is set once, when the chat is created. If you move or rename the chat later, the import leaves that alone.

To link a folder to a project, see Projects.

Reading again

A session that goes on adds to its chat: new messages are added, and messages already imported are not duplicated.

Check all sessions again reads the whole history of the agents once more. It is rarely needed, for example after restoring the workspace from a backup. It creates no duplicates.

Other devices

The setting is kept on the computer, because that is where the agents' history is. Imported chats sync like ordinary ones and can be read on your phone and on other computers. On a phone the Agents section only explains this.

If agents work on two of your computers, turn the import on on each: each one imports its own sessions.

If something is wrong

• Sessions are not being imported with a message about read-only mode: sign in under Settings → Account, or refresh your status there.
• New messages do not appear. The import waits for the agent to finish its answer, and pauses while a sync, a backup, an archive import or an answer of the assistant in MindDuck itself is under way. The app must be open and the workspace unlocked.
• Old sessions are missing. Check Sessions to import. By default Claude Code deletes history older than 30 days by itself; what MindDuck has already imported stays.
• A session went to the wrong project. Move the chat by hand and check in Settings → Folders which projects the folder is linked to: when a folder has several projects, MindDuck does not choose between them.