Orca’s October 10 release adds managed SSH servers and changes to an experimental chat view. But the simpler reason to try Orca is older than either feature: it gives a coding agent its own Git worktree, with terminals and a diff viewer beside it. You can review one task without mixing its edits into your main checkout.
One task, one branch, one agent
Orca calls itself an agent development environment. It is not another AI model: you bring an existing CLI agent such as Codex or Claude Code, plus that provider’s account. Orca opens the agent in a separate Git checkout derived from a chosen branch or commit. Its first-session guide demonstrates three worktrees tackling one task in parallel, but you can learn the workflow with just one.
The practical loop is add repo → create worktree → run agent → inspect diff. Its diff viewer compares a task against its start-from ref and includes staged, unstaged, and untracked changes. This is more useful than watching three terminal transcripts if the goal is to decide what code should survive. The worktrees remain ordinary Git worktrees; Orca is a graphical organizer, not a new version-control system.
Try one agent before three
You need a local Git repository and an installed, signed-in coding-agent CLI. The installation guide offers macOS, Windows, and Linux builds; Orca does not supply the model or your provider subscription. Here is a deliberately small first session, adapted from Orca’s official walkthrough:
- Install Orca, open it, and choose Add Repo. Point it at a local project you can safely edit, preferably one with a working test command.
- Click + beside that repo. Name the task
add-one-test, leave the start-from ref on your intended base branch, and create the worktree. Orca opens a separate checkout rather than editing the main folder. - Choose your already-installed CLI in the agent selector. For Codex, Orca’s guide says to install Codex and log in separately first. Give it a bounded prompt: “Add one test for an existing function. Run only the relevant tests. Do not commit or push. Tell me what changed.”
- Open the worktree’s diff view. Read the test and any unexpected edits, rerun the relevant test yourself, then decide whether to stage or discard. Orca can commit and push, but do that only after review. You do not need three agents or a phone to finish this exercise.
Where isolation ends
A separate checkout prevents simultaneous agents from overwriting the same working files; it does not sandbox what their CLIs can read, execute, or send to their model providers. Review agent permissions and repo secrets before giving access. Orca’s privacy documentation describes anonymous product telemetry and a toggle under Settings → Privacy; that telemetry is distinct from traffic to the agent provider. Remote SSH hosts and mobile pairing are optional, not part of this local tutorial.
The October 10 release also labels native chat experimental and lists known update and downgrade issues. Start with the ordinary terminal workflow rather than treating every newer surface as required. No independent productivity benchmark is established by the site’s “100x” tagline, and this walkthrough was checked against documentation rather than exercised in a local Orca installation.
Before adopting it
- Start with one disposable task and confirm the agent is operating in the intended worktree, not
main. - Inspect the complete diff, including untracked files; run the test command outside the agent’s summary.
- Keep each agent’s provider permissions and Orca’s telemetry setting separate in your privacy review.
- Do not delete a worktree until you have checked whether its branch holds changes you still need.