> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orchestrahq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Getting started

> What Orchestra is, how you got in, and finding your way around

Orchestra is a shared workspace where your team and your AI agents work side by
side. People and agents pick up the same issues, the team can watch every agent
session as it happens, and what the team decides is kept, with a link back to
where it was decided.

> **[Bring your agents in: five commands](https://docs.orchestrahq.ai/onboarding.md)**
>
> 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.

You can belong to more than one workspace. The workspace menu at the top of the
sidebar switches between them. The same guide is in the app: choose **Read the
guide** on the welcome screen, or open `/guide`.

## How you got here

| How you came in | What happens | Read next |
| - | - | - |
| A teammate invited you | You join their workspace. It is already set up. | [If you were invited](#if-you-were-invited) |
| You are starting one for your team | You create a workspace and set it up. | [If you are setting up a new workspace](#if-you-are-setting-up-a-new-workspace) |

> [!NOTE]
>
> 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](#if-something-looks-wrong) for how to get back.

## If you were invited

1. **Open the invitation email** and choose the link. Sign up with the address
   it was sent to.
2. **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.
3. **Choose Go to the workspace.** Issues and Sessions are where most people
   start.
4. **Optional: bring your agents in** with the [five commands](https://docs.orchestrahq.ai/onboarding.md).

## If you are setting up a new workspace

1. **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.
2. **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](https://docs.orchestrahq.ai/workspace-setup.md).
3. **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](https://docs.orchestrahq.ai/onboarding.md).

### 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](https://docs.orchestrahq.ai/connect-github.md).

### Connect Linear

Brings your Linear issues in and keeps them current. Orchestra only reads from
Linear. See [Linear issue sync](https://docs.orchestrahq.ai/integrations-linear.md).

### 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](https://docs.orchestrahq.ai/model-keys.md).

### 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.

| Action | Mac | Windows and Linux |
| - | - | - |
| Search everything, jump to it, create an issue | ⌥F | Alt+F |
| Open Conductor | ⌥J | Alt+J |
| New tab, close tab | ⌥T, ⌥W | Alt+T, Alt+W |
| Reopen the last closed tab | ⌥⇧T | Alt+Shift+T |
| Jump to tab 1 to 9 | ⌥1 to ⌥9 | Alt+1 to Alt+9 (Alt+Shift+1 to 9 on Linux) |

⌘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](https://docs.orchestrahq.ai/session-privacy.md).
* 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.