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

# Quickstart

> Connect a workspace and run your first task with the agent team.

This guide takes you from a fresh install to your first completed task. It takes a
few minutes.

## 1. Create a workspace

A **workspace** is your unit of context, it holds your sources (repositories or
folders), agents, issues and knowledge base.

When you open Orkestral for the first time, create a workspace and give it a name
(for example, your product's name).

## 2. Connect a source

Add a **source**, a local repository or folder. Orkestral reads and maps it so the
agents understand your stack, structure and conventions before doing anything.

<Tip>
  You can add more than one source to the same workspace. The agents read across
  all of them.
</Tip>

## 3. Hire your team

Ask the **CEO** agent (in chat) to assemble a team. It proposes an initial roster,
typically a **Tech Lead**, a **Code Reviewer** and the specialists your project
needs (Frontend, Backend, DevOps...), with a proper reporting hierarchy.

## 4. Ask for something

Talk to the CEO in natural language. Describe what you want, a feature, a fix, a
refactor. You don't need to specify *how*.

```text theme={null}
Add a dark-mode toggle to the settings page and persist the choice.
```

Here's what happens behind the scenes:

<Steps>
  <Step title="Plan">
    The CEO reads the relevant code, breaks the request into **issues**, and
    delegates to the right specialists.
  </Step>

  <Step title="Execute">
    Specialists run the work. The **Forge** applies code changes locally, at no API
    cost, and only escalates to a premium model when needed.
  </Step>

  <Step title="Review">
    The **Code Reviewer** validates the changes. Verdicts (approved / changes
    requested) come back to you in chat.
  </Step>

  <Step title="Report">
    You get a clear summary of what was done, with the issues and code changes
    linked.
  </Step>
</Steps>

## 5. Route to a specialist

Mention an agent with `@` to send a turn directly to them, for example
`@Code Reviewer take a look at this PR`. That agent picks up the chat context and
does the work itself.

## Next steps

<CardGroup cols={2}>
  <Card title="The agent team" icon="users" href="/en/introduction">
    How the CEO, Tech Lead, Code Reviewer and specialists work together.
  </Card>

  <Card title="Forge, local execution" icon="bolt" href="/en/introduction">
    How the local model executes changes at \$0 API cost.
  </Card>
</CardGroup>

<Note>
  More guides (Issues & epics, Code review, Knowledge base, Integrations) are on the
  way.
</Note>