Saved workspace & resume

Orchestra saves project folders and names, sidebar order, session names, agent choices, worktree locations, captured conversation IDs, and selection state. Each project remembers its last selected session.

On launch, Orchestra opens the Startup View from Settings without starting agent processes. Selecting a restored session starts or resumes its CLI in its folder.

Right-click an ended session and choose Resume Session, or use the resume button above its terminal. The action reopens the saved conversation using the agent ID. It does not send the original task again.

Claude Code, Pi and Grok Build sessions use the Orchestra session UUID as their own session ID, then resume with that ID. Other CLIs capture their own conversation IDs. The conversation history is owned by the agent CLI and must still be available on your computer.

Some agents only create a resumable conversation after work has begun. Vibe, for example, requires a saved conversation in its session logs.

If Orchestra has no ID for a previously launched session, it requires an explicit Start New Conversation action. It does not guess by selecting an unrelated recent conversation.

Live processes and terminal scrollback are not persisted. Resume restores the agent conversation through its CLI; it does not restore a still-running shell process. Plain terminals start a fresh shell.

Workspace metadata is local. See Settings & storage for file locations and messaging history behavior.