FAQ

Yes. Download the latest macOS or Linux build from GitHub Releases. Installation covers first launch and building from source.

Orchestra checks for new versions on its own and offers to install them. See Updates.

Yes. Orchestra is released under the MIT License, and its source code is on GitHub.

Open an issue on GitHub Issues. For a bug, include your Orchestra version from the About panel, your operating system, the agent you used, and the steps that reproduce it. See Contributing to send a change.

Orchestra uses your installed coding CLIs with their existing credentials and configuration. Model access and billing continue to be handled by each agent’s provider.

By default, yes. New sessions start in a new worktree under ~/.orchestra/worktrees, on a branch named orchestra/<agent>-<id>. Clear Create a new worktree to work in the project folder instead. Work on and Review always use a new worktree.

Remove the worktree is checked by default. Orchestra removes only a clean checkout and keeps a branch with unmerged commits. Clear the checkbox to keep the worktree.

Sessions start in each agent’s auto mode or its closest safe equivalent. Orchestra never uses full permission bypass flags.

The process may have ended, or the agent may not provide activity events. OpenCode, Mistral Vibe, Antigravity, and Grok Build currently have no activity integration. For Codex, check that Orchestra’s hooks are trusted.

Not by default. Sending a request puts it in the receiving session’s inbox. Ask the recipient agent to read it with orchestra session inbox, or choose Execute Request in the app. To have requests submitted automatically once the recipient is free, turn on Settings → Agents → Deliver Inbox Requests Automatically.

Orchestra saves project and session metadata. Live processes and terminal scrollback end when the app quits. A captured conversation ID allows Resume Session to continue that agent’s saved conversation.