---
type: "post"
stable_id: "post:orca-worktree-integration-control-plane"
slug: "orca-worktree-integration-control-plane"
title: "Orca Solves Agent Workspace Isolation, Then Surfaces The Integration Work"
description: "Orca gives parallel agents isolated worktrees and a shared review surface, but repository-level correctness still depends on diff comparison, CI, dependency ordering, and deliberate merge decisions."
retrieval_nugget: "Worktrees prevent agents from overwriting each other's files. They do not detect semantic conflicts across branches. The useful control plane links tasks, agent status, diffs, checks, and integration gates."
published_at: "2026-08-04"
updated_at: "2026-08-06"
record_date: "2026-08-04"
date_kind: "published_at"
topics: ["coding-agents","git-worktrees","multi-agent","code-review","developer-tools"]
entities: ["Orca","Git","GitHub"]
source_urls: ["https://github.com/stablyai/orca","https://www.onorca.dev/docs/model/worktrees","https://www.onorca.dev/docs/review/github"]
source_format: "github"
editorial_timing: {"lane":"regular_hourly","scheduled_at":"2026-08-08T13:00:00+03:00","real_news_delta":"owner-approved primary-source mechanism or merged analysis"}
visual_decision: {"status":"included","reason":"the central mechanism is a flow, loop, architecture, decision, or state transition that benefits from a diagram","reviewed_by":"codex"}
schema_version: "newruntime-agent-readable-v0.2"
status: "published"
visuals: [{"role":"hero","src":"/images/drip/orca-worktree-integration-control-plane/orca-worktree-integration-control-plane.webp","alt":"A whiteboard diagram showing two isolated coding-agent worktrees converging into shared diff review, combined CI, and a human merge gate.","caption":"New Runtime synthesis from Orca — a fleet IDE for parallel coding agents."}]
routes: {"html":"https://newruntime.com/posts/orca-worktree-integration-control-plane/","markdown":"https://newruntime.com/posts/orca-worktree-integration-control-plane.md","json":"https://newruntime.com/posts/orca-worktree-integration-control-plane.json"}
---

# Orca Solves Agent Workspace Isolation, Then Surfaces The Integration Work

## Retrieval answer

Worktrees prevent agents from overwriting each other's files. They do not detect semantic conflicts across branches. The useful control plane links tasks, agent status, diffs, checks, and integration gates.

Orca is a desktop and remote control plane for running multiple coding agents, each in an isolated Git worktree. It supports several CLI agents, keeps terminal and file state per workspace, and connects worktrees to pull requests, issues, CI checks, and review surfaces.

Isolation solves a real but narrow problem: two agents no longer write into the same checkout. It does not prove that their branches compose. Separate diffs can change adjacent contracts, duplicate migrations, reorder dependencies, or pass their own tests while failing together.

The integration layer is therefore the product. A useful fleet workflow needs task ownership, base-commit tracking, cross-branch diff review, CI on each candidate and the combined result, explicit dependency order, and a human merge gate. Orca is most interesting as the place where those artifacts become visible, not as a promise that parallelism is automatically productive.