Kapacitor/Hosted agents

Launch a coding agent from any browser.

A daemon on your machine spawns Claude Code or Codex in an isolated worktree. You start the work from the dashboard — phone, laptop, anywhere — and a teammate can join the same prompt.

01 · Launch

Start an agent without opening a terminal. A daemon on your dev machine does the work.

Ready Launch hosted agent

Daemonlaptop

VendorClaude Code

Repocheckout-api

Branchmain → isolated worktree

Run kapacitor daemon start -d once on a machine that holds your repos. The dashboard sees every running daemon and lists only the vendors it can actually spawn. No terminal, no SSH, no waking the laptop.

You · from a browser

Open the dashboard, pick the checkout-api repo on my laptop daemon, hand the agent the spec, and start.

Agent · claude code

Checked out spec/webhook-replay in a new worktree. I’ll read the spec and propose the first acceptance case before touching code.

Live terminal · streamed to the dashboard

02 · Pair or mob

More than one teammate can drive. Same session, different operators, attributed turns.

Running Codex · hosted agent

Repobilling-service

Shared withAna, Rafael, Priya

Inputtext, keys, permission answers

Attributionper turn, GitHub identity

Anyone with view access on a hosted session can send input — text, special keys, even permission answers. Every message is stamped with the sender’s GitHub identity. Pair programming without screen-sharing, mob programming without a meeting.

Ana

Before you touch the ledger write, show the refund path you found.

Rafael

And run the idempotency replay test after the patch. That one flakes.

Agent

Refunds enter through RefundRequestedHandler and write to ledger_entries after the gateway callback.

I’ll patch the callback branch and run refund_idempotency_replay before summarising.

One session · multiple operators

03 · Isolation

Your main checkout stays untouched. The agent gets its own worktree, sandbox, and approval bridge.

Hosted worktree

billing-service / fix/refund-ledger

Worktree: Fresh checkout, isolated from your local branches.
Codex sandbox: workspace-write — file edits in the worktree only.
Approvals: Sensitive operations bubble up to the dashboard’s permission bridge.
Shutdown: Daemon stop sends graceful /exit; no zombie sessions.

Run several agents in parallel without juggling terminal tabs or worrying about which branch is checked out where. The daemon gives each session its own worktree, applies the sandbox defaults, and ends cleanly when you stop it.

How it works

kapacitor daemon start on your machine. The daemon advertises itself to your tenant over SignalR; the dashboard’s launch dialog picks a vendor, repo, and branch, and the daemon spawns the agent in an isolated worktree. Multi-user input is FIFO and attributed per turn. Read the mechanics in Hosted agents and CLI configuration.

Run your team's agents from anywhere.

Kapacitor is in private preview. We'll help you set up a daemon on a dev machine and get your team driving hosted agents from the dashboard.

Rather start a conversation? Talk to the team — we’re building with teams that already use coding agents.

Built by the team behind KurrentDB — event streams in production are what we do. Coding agents just produce a new kind.