Launch a coding agent from any browser.
A daemon on your machine spawns your coding agent in an isolated worktree. You start the work from the dashboard — phone, laptop, anywhere — and a teammate can join the same prompt.
Starting work means opening a terminal on the right machine.
No SSH, no waking the laptop, no “are you on the billing-service checkout?”. Without a daemon, the agent lives where you happen to be sitting.
Can you pick this up? I’m on my phone. The repo is on my desk machine.
I can only run where this shell is. You’ll need to open a terminal on that laptop.
Without a hosted agent, remoting is a meeting or a hop.
Start an agent without opening a terminal.
Run kcap daemon start -d once. The dashboard sees every running daemon and lists only the vendors it can actually spawn. A teammate can join the same session.
Open checkout-api on my laptop daemon, hand the agent the spec, and start.
Checked out spec/webhook-replay in a new worktree. I’ll read the spec and propose the first acceptance case before touching code.
With a hosted agent, the work is on the dashboard, not on whoever has the laptop open.
kcap daemon start on your machine. The daemon advertises itself to your Capacitor server; the dashboard’s launch dialog picks a vendor, repo, and branch, and the daemon spawns the agent in an isolated worktree. See Hosted agents.
Run your team’s agents from anywhere.
Start free — set up a daemon on a dev machine and drive hosted agents from the dashboard with your team.
Fix flaky auth-token refresh test
Tried mocking the clock first — abandoned after the race persisted. Root cause: token cache TTL rounding. Patched in auth/cache.ts, added regression test. Two approaches rejected, one shipped.