Settings & storage

• Startup View: the last selection, the Scratchpad, or Issues & PRs when available.
• Confirm Before Quitting: ask before quitting while sessions are running.
• Confirm Before Closing a Session: ask before stopping and removing a session. When off, sessions close immediately and keep their worktrees.
• GitHub Auto Refresh: manual, or every 30 seconds, minute, or 5 minutes.

In Settings → Agents:

• Default Agent: preselected for new sessions and used by Work on and Review.
• Deliver Inbox Requests Automatically: off by default. When on, queued requests are submitted to the recipient once its agent finishes its turn, oldest first. See Session messaging.
• Agent Skill: install the Orchestra skill for your agents.

Appearance and terminal settings are described in Appearance; telemetry is in Privacy & usage data.

Orchestra checks GitHub Releases at startup and once a day. Turn this off with Settings → General → Check for Updates Automatically, and turn on Include Beta Versions to be offered pre-releases too. To check now, choose Check for Updates… in Settings → General or the command bar, or in the File menu on macOS.

When a version is available, install it and restart, install it when you quit, skip it, or decide later. Orchestra verifies the download against the release’s checksums before replacing the app; on macOS it also checks that the new app is signed and notarized. Restarting stops running sessions; Orchestra warns you first. If Orchestra cannot write to the folder it runs from, download the new version yourself.

On Linux, Settings → General also shows the version and commit; on macOS they are in the About panel.

A versioned JSON file stores preferences, project folders, session metadata, captured agent conversation IDs, and selections. Writes are atomic. The snapshot contains no terminal scrollback or live process state.

Worktrees created for sessions live outside your project folder:

A local JSON file stores session messaging history: queued and running requests plus the newest 500 finished ones from the last 30 days. Unread requests survive restarts. If the file is unreadable, Orchestra moves it to collaboration.json.corrupt and starts a new history. Claimed requests become interrupted during shutdown or recovery and are not automatically resubmitted.

Authentication, global configuration, and native conversation histories belong to each agent CLI. Orchestra uses those existing accounts and tools. On macOS, your OpenRouter management key is kept in the Keychain.

Vibe session logs are isolated by Orchestra session under: