Conversation history

Cmdop keeps one durable conversation history per machine — messages, tool activity, and result artifacts — held by the computer that did the work rather than by the browser that displayed it, so you can return later from any client and read what happened. History records the past; it is not the live execution state you reattach to.

That is why you can close everything, come back later, and read what happened — from a different client if you like.

One history per machine, readable by engine

A machine has one chronological history. Each session within it keeps the engine that created it, so history renders which engine performed a past piece of work. The Claude Code and Codex views are filtered views of that same machine-scoped history, not separate databases.

History is not execution state

This distinction matters more than it sounds.

History is the durable record of what happened. Execution state is the live thing you attach to when you reattach to a session — and it is not reconstructed for you by replaying that record. When you come back to running work, you are observing it directly, not watching a rebuild.

The practical consequence: resuming a conversation is not the same operation as “loading a transcript into a fresh context”. A session that is still alive is still alive.

Engines keep their own working memory

Cmdop’s durable history is a product guarantee. What an execution engine holds in its own working context during a run is that engine’s behavior, and it differs between CMDOP, Claude Code, and Codex. Do not assume the two are the same thing.

Common questions

What does Cmdop save in conversation history?

Cmdop saves messages, tool activity, and result artifacts for the machine that did the work.

Is conversation history the same as live execution state?

No. History records what happened. Live execution state is the running session you reattach to directly when work is still active.

Do Claude Code and Codex have separate Cmdop histories?

No. They are engine views over the same machine-scoped history. Each session still records which engine performed its work.

Related

• Conversations and sessions
• Execution engines
• Persistent Memory Is Not Persistent Execution State — the deeper treatment.