Workstation
Work where the repository already lives
A launched local agent gets a real git worktree, the repository setup and explicitly allowed build caches. Source stays on that workstation unless you choose a workflow that uploads it.
Agent platform
One operator seat for agents wherever they run.
Start beside your local toolchain, move an interactive session to cloud capacity, or let CI wake a tightly scoped Factory agent. Hive keeps the session, branch, PR, CI and spend in one workspace.
The lanes share a control plane—not one undifferentiated security model.
Agents workspace · live roster
Different execution lanes. One operational picture.
Every attached session can report its phase, plan, worktree state, branch, pull request and current Hive run into the same owner-only workspace.
WORKSTATIONreal worktree · local tools
CLOUDephemeral pod · interactive
FACTORYCI task · reviewed wrapper
- Local
- Your worktree and toolchain
- Cloud
- Ephemeral interactive sessions
- Factory
- Policy-wrapped CI agents
Three execution lanes
Choose the boundary that fits the task.
Hive does not pretend a laptop shell and a CI container are the same thing. It gives each lane the controls and containment its job requires.
Cloud
Free the laptop without losing the session
An interactive Pi session runs in an ephemeral, resource-capped pod. Steer it from the browser, then let the delivery wrapper preserve its commits and PR.
Factory
Let CI open a bounded coding task
A pinned Pi runtime runs as an ordinary Hive workload. Compiled context, reviewed capabilities, budgets and git policy stay outside the model.
Workspace
Operate the fleet from one place
Live transcript, plan, workflow, files, branch, PR, CI and approvals sit beside each session instead of across terminal tabs.
Teams
Coordinate work without hiding collisions
Group sessions into a team, see branches and claims together, pass durable notes, and surface overlapping work before delivery.
Ownership
Controls follow the person and the lane
Conversations are owner-only by default. Viewer shares are read-only; drive access is reserved for cloud sessions, where the owner’s machine is not exposed.
Native integration
The agent does not sit beside CI. It is inside the same control loop.
Hive already knows the run, tests, branch and delivery state. Agents receive narrow calls to that system instead of credentials to scrape it.
Observe
Sessions stream into the browser.
Follow turns, tool calls, costs, plans, workflows and attention state without attaching to the machine that hosts the agent.
Act
Steer, interrupt and approve.
Owner controls ride a durable command channel. A queued command remains visible until the client claims and reports it.
Verify
The branch and CI tell the truth.
Working-tree state, pull request and Hive checks share the rail, so “done” is measured against delivery rather than the last assistant message.
Access model
Sharing is explicit, and write access is narrower than read access.
The UI explains which controls are possible instead of rendering every session as equally steerable.
Owner
Every own sessionRead · steer · interrupt · approve · end
Viewer
Named read-only shareRead transcript and live stream
Driver
Cloud sessions onlySteer · interrupt · switch model
Factory observer
No workstation controlRun, transcript, result and spend
| Role | Controls | Available on |
|---|---|---|
| Owner | Read · steer · interrupt · approve · end | Every own session |
| Viewer | Read transcript and live stream | Named read-only share |
| Driver | Steer · interrupt · switch model | Cloud sessions only |
| Factory observer | Run, transcript, result and spend | No workstation control |
Under the surface
See the harness and the platform that make these lanes one system.
Private beta
Bring one repository. See the whole system work.
Start on your own runner, keep your existing CI beside it, and watch Hive turn the next eligible red check into a reviewable fix.