Runs and conversations

A run is a conversation with an agent. It records your initial goal, follow-up turns, tool calls, attachments, outputs, and usage. Code runs belong to a workspace and appear as chat tabs. Work and Chat runs can belong to a collection or stand alone.

​

Read the transcript

Final answers remain visible while progress commentary can fold away. Open tool details when you need their full input and output. Long conversations load recent messages first. Scroll up for earlier history and choose Jump to latest to return to the active turn.

​

Context and usage

Hover the context ring to see the breakdown of messages, tools, skills, memory, system instructions, free space, and compaction reserve when the provider reports it. Hover a response’s duration to inspect its usage. Counts and cost estimates depend on what the provider reports; they are not a billing statement. When context compaction occurs, the transcript shows Compacting context… and a divider after it finishes.

​

Continue and fork

Send a follow-up to continue the same provider session. Model, effort, permissions, and other supported conversation settings stay with that chat. Use Fork beside a response to explore another path. Claude, Codex, and Cursor support forking; Copilot does not. Forked conversations retain the source run’s saved attachments. A run also keeps its original mode when resumed or forked.

​

Work in the background

Switching chats or workspaces does not stop a run. Background cards, notifications, and the menu bar help you find work that is running or needs input. Use Stop to cancel active work. Stopping a run does not undo file changes; inspect turn changes to decide what to keep. Codex supports queued messages and steering. Its voice conversations can delegate larger jobs to separate visible chats.

​

Keep attachments and results

Files and images you attach are saved with the conversation. You can reopen or download originals later. Archiving retains them; deleting their last owning conversation removes run-owned copies. Work’s session panel separates Sources from Deliverables. Atlas also lists generated files and uploads. Choose Save to Atlas to keep a permanent copy before deleting its conversation.

​

Archive

Archive a run to remove it from the active chat list without deleting its history. Restore it from Settings → Archive.