orchestra / docs
Documentation/Workspace

Supported agents

Use the agent CLIs you already know, with their own configuration and credentials.

On this page Choose your agentAuto modeRead the activity indicatorEnable Codex statusHow integrations are loaded

Choose your agent

AgentCommandActivity status
Claude CodeclaudeHooks
CodexcodexHooks
PipiBundled extension
Mistral VibevibeNot integrated
OpenCodeopencodeNot integrated
Antigravity CLIagyNot integrated
Grok BuildgrokNot integrated

Claude Code is the Default Agent unless you choose another in Settings. Install and authenticate the CLIs you want to use, then choose one when creating a session. Orchestra does not supply model access or replace an agent’s subscription.

Auto mode

New sessions start in each agent’s auto mode, or the closest safe equivalent. Full permission bypass flags are never used.

AgentMode
Claude Code--permission-mode auto
Codex--approve-for-me
Grok Build--permission-mode auto
Antigravity CLI--mode accept-edits (edits only)
PiNo approval prompts
OpenCode, Mistral VibeThe CLI’s default prompts

Read the activity indicator

The dot sits at the end of each session row and is repeated in the status bar.

  • Green: the agent is waiting for input.
  • Yellow, pulsing: the agent is working. With Reduce Motion, the dot stays still.
  • Gray: activity status is unavailable, or the process has ended.

OpenCode, Mistral Vibe, Antigravity, and Grok Build currently have no activity integration, so their dots stay gray. A gray dot alone does not mean that an agent is idle.

Enable Codex status

Codex may ask you to review and trust Orchestra’s process-scoped hooks. If status remains gray, use Enable Codex status… or review the hooks with /hooks inside Codex.

Codex’s exit footer also provides a fallback for capturing the conversation ID used by Resume Session.

How integrations are loaded

Orchestra launches your existing CLI with process-local integration settings. Claude and Codex use hooks; Pi loads a bundled extension; OpenCode loads a bundled session capture plugin. Vibe writes session logs under ~/.orchestra/AgentSessions/Vibe. Antigravity’s conversation ID is captured from its exit footer. Claude Code, Pi and Grok Build receive the Orchestra session UUID as their session ID when the session starts.

Credentials and global agent settings remain owned by each CLI. See resume behavior for saved conversations.

Browse documentation

Welcome to OrchestraA macOS workspace for your projects, terminals, and coding agents.
InstallationDownload Orchestra from GitHub Releases, or build it from source.
Projects & sessionsOrganize your work around folders, with an isolated worktree and terminal for every session.
Supported agentsUse the agent CLIs you already know, with their own configuration and credentials.
TerminalA real interactive terminal, running your agent or shell in its own folder.
Sidebar & navigationArrange the sidebar, switch projects with Arc Mode, and keep track of activity.
Saved workspace & resumeReturn to your projects and continue a captured agent conversation.
Issues & pull requestsRead and triage repository context, then start an agent session without leaving Orchestra.
Session messagingExchange requests and replies between existing sessions in the same project.
AppearanceChoose a palette for the whole workspace, including your terminals.
Custom themesCreate your own palette in a JSON file and use it beside the built-in themes.
UsageSee subscription limits for your agents and OpenRouter spend by model.
Settings & storageGeneral preferences and where Orchestra keeps workspace metadata and message history.
Privacy & usage dataOptional anonymous usage sharing, approximate city and country, and every collected event.
Keyboard shortcutsThe everyday actions you can reach from the keyboard.
ContributingReport issues, propose changes, and build Orchestra locally.
FAQAnswers to the questions that come up before your first session.
↑↓ Navigate↵ Openesc Close