Skip to content
Go To Dashboard

Sessions

An Agent Studio session is one Claude Code or Codex process and conversation in one absolute working directory. You can keep several live sessions for an agent or folder and switch among them as tabs.

New session starts a fresh process using the coding agent selected for that session. Studio uses the conversation title when one is available, falls back to the folder name, and gives a name you set yourself precedence. Closing a live tab asks for confirmation and then ends that terminal process. Exited sessions move into history.

These states answer different questions:

StateQuestion answered
RunningIs the terminal process alive?
ReadyCan Studio safely send programmatic input to the agent?
FocusedWhich agent or folder is the UI showing?
ActiveWhich tab receives keyboard and image input?
BoundWhich agent project do Canvas and direct actions target?

A session can be running but not ready while the coding agent shows a trust, authentication, or first-run prompt. Use the visible terminal to finish that prompt. Focusing another agent changes the UI subject; focusing does not rebind the session.

Open History in the rail to search sessions Studio has recorded and conversations still available from Claude Code or Codex. Studio checks recent working directories, merges the sources, removes duplicate entries, and shows the newest results first.

Selecting a history row opens its recorded events for review. Reviewing a row does not launch a process. Choose a continuation action only after confirming the directory and the context you need.

ChoiceWhat happensFidelity
ResumeStudio verifies the original coding-agent conversation still exists, then asks that same coding agent to resume it in the recorded directory.The coding agent owns and restores its native conversation. Studio reuses the tracked session and binding when available.
Continue hereStudio starts a new conversation with the same coding agent in the same directory and injects a bounded brief assembled from Studio events. When the source is a Studio-tracked session there, the new session also preserves its recorded project binding.This is a briefing, not restored model context, a terminal replay, or the coding agent’s native conversation record. The new session must inspect the repository.
New sessionStudio starts a normal fresh conversation in the chosen directory.Nothing from the earlier conversation is carried automatically.

Native Resume is offered only after Studio checks the selected coding agent’s history. If that verification fails, use Continue here. A history item without a matching Studio record can still open as an ordinary fresh session, but no Studio brief is available.

The portable brief favors recent context: roughly the newest 12 turns, shortened prompt and reply text, recent tool activity, up to 30 referenced paths, and up to 10 recent commands. It says when material was omitted. A transcript-only row has no prior Studio binding to preserve, and a missing brief starts nothing under the guise of a continuation. Even when a tracked binding carries forward, confirm the active tab and bound agent before using a direct action.

Open Quick Jump with +K or +P on macOS, or Ctrl+K or Ctrl+P elsewhere. It searches live sessions, past sessions, agent projects, and recent folders, and it can open the template browser. Use /, Enter, and Escape to navigate.

Choosing an agent or folder from Quick Jump can start a fresh session when no suitable live tab exists, so it is more than a navigation-only menu.

Use +1 through +9 on macOS, or Ctrl+1 through Ctrl+9 elsewhere, to select the corresponding live tab for the currently focused agent. Tabs are numbered oldest first.