Files
archived-orca/docs/site/content/docs/first-session.mdx
Neil 2c0c6ac0c4 docs: stop promising cross-worktree split panes and Shift-Enter split in Jump Palette (#33902)
Panes are scoped to a single worktree and the Jump Palette has no
Shift-Enter handler, so replace those promises with the real flow:
watch sidebar status indicators and jump between worktrees with
Cmd-J (macOS) / Ctrl-Shift-J (Windows / Linux).

Fixes #10477
2026-10-26 03:45:32 -07:00

54 lines
2.9 KiB
Plaintext
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
title: Your first 3-agent session
description: From empty app to three agents running in parallel in under five minutes.
---
import { Callout } from '@/components/docs/prose'
This is the single most important page in the docs. By the end you'll have three agents running in parallel on three different approaches to the same task, with one PR shipped.
## 1. Add a repository
Click **Add Repo** on the sidebar and point Orca at a local checkout. Orca reads the repo's git state and picks up your default branch as its **base ref** — the ref every new worktree branches from.
You can change the base ref later under the repo's settings.
## 2. Create a worktree
Click the **+** next to the repo name. Type a task name ("fix-login-race" is fine — if you leave it blank, Orca names it after a marine creature).
The launcher opens with your **default agent** preselected (configurable under [Settings → Agents](/docs/settings)) or an empty terminal if you'd rather start cold. Pinned worktrees stand out in the sidebar so the ones you actually live in stay visible.
Pick a **start-from** ref. Most of the time this is your base ref (`origin/main`), but you can start from any branch or commit.
Orca creates a real git worktree under its managed directory, checks out the branch, and opens it.
## 3. Pick an agent
In the new worktree, a terminal opens with an **agent combobox**. Pick Claude Code, Codex, Cursor CLI, or any of the [supported agents](/docs/agents/supported). Orca will launch the agent's CLI with the correct working directory and forward your subscription credentials.
## 4. Race three agents on the same task
Now repeat steps 2–3 twice more. You now have three worktrees:
- `fix-login-race` → Claude Code
- `fix-login-race-2` → Codex
- `fix-login-race-3` → Cursor CLI
Paste the same prompt into each. Three branches. Three diffs. Same prompt. Let them work.
## 5. Watch all three agents
Each worktree keeps its own pane layout, so switching worktrees swaps the whole view. Watch the sidebar's [status indicators](/docs/model/agents-sessions#state-indicators) to see which agent is working, done, or waiting on you, then jump to it from the sidebar or with `Cmd-J` (macOS) / `Ctrl-Shift-J` (Windows / Linux). Inside a worktree, drag a tab to a pane edge to split it — see [Tabs, panes & split layouts](/docs/model/tabs-panes-splits).
## 6. Pick a winner, review the diff, ship it
Once agents settle, open each worktree's diff view. Use [Annotate AI Diff](/docs/review/annotate-ai-diff) to leave inline comments and send them back to whichever agent got closest.
Commit and push directly from Orca — see [Commit & push from Orca](/docs/review/commit-push). The other two worktrees can be deleted with one click; their branches go with them.
<Callout title="That's it">
This flow — add → worktree → agent → watch → diff → ship — is the whole of Orca. Every other page
in these docs is a deeper look at one of those steps.
</Callout>