Bring your agents in: five commands
Install the CLI, sign in, and see your agent sessions in the workspace. About
five minutes.
What Orchestra is
A workspace belongs to one team. Everyone in it sees the same things:- Issues: the work. An issue can be assigned to a person or to an agent.
- Sessions: every agent session your team runs, live. Teammates can follow along and steer.
- Knowledge: docs, and a decision log for every issue.
- Inbox: what needs you, such as an issue assigned to you or a mention.
/guide.
How you got here
If a teammate invited you, sign up from the link in their email. Creating a
new workspace of your own instead is the most common wrong turn. See
If something looks wrong for how to get back.
If you were invited
- Open the invitation email and choose the link. Sign up with the address it was sent to.
- You land in your team’s workspace, on a welcome page that shows what is already connected. There is nothing for you to set up.
- Choose Go to the workspace. Issues and Sessions are where most people start.
- Optional: bring your agents in with the five commands.
If you are setting up a new workspace
- Sign up and create a workspace. While Orchestra is invite only, a new workspace waits until Orchestra lets it in. The app says so, and opens once it is.
- Walk through setup: name the workspace, connect GitHub, connect Linear, invite teammates, install the CLI. Every step can be skipped. See Setting up a workspace.
- Create your first issue and invite your team.
Connecting your tools
Each of these is optional, and each is also a step in setup. GitHub, Linear and the model key are set once for the whole workspace, usually by whoever runs it. The CLI is per person.Install the CLI
Brings the agents you run on your own machine (Claude Code, Codex, Gemini CLI, Cursor, OpenCode) into the workspace, live. Five commands: see Onboarding.Connect GitHub
Lets agents work on your repositories in cloud sessions. In Settings, Integrations, choose Connect GitHub and pick only the repositories you want. See Connect GitHub.Connect Linear
Brings your Linear issues in and keeps them current. Orchestra only reads from Linear. See Linear issue sync.Add your own model key
Which key cloud sessions run on, and how to add your own Anthropic API key: see Your own model key.Invite teammates
In setup’s Invite teammates step, or Settings, People, enter email addresses and choose Send invites.Finding your way around
- Sidebar: Conductor, Inbox, Issues, Sessions and Knowledge. Settings is at the foot, beside your name.
- Tabs: whatever you open opens in a tab across the top, and your tabs come back when you reload.
- Shortcuts: Option on a Mac, Alt on Windows and Linux. The app labels every shortcut for the system you are on.
⌘K (Ctrl+K) is not search. Search is ⌥F (Alt+F).
On the Issues list, C creates an issue, and S, P and A set the
selected issue’s status, priority and assignee.
Anything tagged Preview shows what is coming, on sample data. Nothing in a
preview reads or changes your workspace.
Working with agents
- A session is shared with your workspace by default: everyone in it can watch it live and read its summary afterwards.
- You can start a session private, or make one private later. See Session privacy.
- Where cloud sessions are on, an issue can also start one in the cloud, on a connected GitHub repository.
If something looks wrong
- “Your workspace is not invited yet.” You most likely created a new workspace instead of joining your teammate’s. If that page lists an invitation to your team’s workspace, choose Join; if your team’s workspace is listed, choose Open. Otherwise ask your teammate to invite you again.
- You were invited, but you see setup steps. You were probably invited as an admin. Choose Skip for now on each step. Nothing breaks.
- The invitation does not work. It may have expired, or you signed up with a different address. Ask for a new one, to the address you sign in with.
- A teammate mentioned a session you cannot see. It may be private. Its page says who can give you access.