About
We build tools for engineers running AI agents.
Every job gets its own Thread: its plan, its notes, its keys. Agents pick up where the last one stopped, and use those keys without ever seeing the values.
Why Forkbench?
Most terminals were designed for one human typing at one prompt at a time. The moment you start running AI coding agents in parallel , one fixing a flaky test, another sketching a new feature, a third explaining a stack trace, that mental model breaks down. Tabs explode. Work gets lost. You spend more time juggling sessions than shipping.
Forkbench fixes that. It organizes your terminal tabs, where each tab runs its own isolated session, into one Thread per piece of work. Forkbench groups the CLI agents running in these sessions and provides a shared task and communication system so they coordinate and work as a team. The knowledge that guides them lives in shared, private notebooks; git stays managed underneath; and you see the whole board from your Mac, the web, or your phone. You stay in control, and ship faster.
Who we built it for
- Engineers running several AI coding agents at once, tired of tab gymnastics and losing the thread.
- Anyone whose agents now span more than one machine and who needs a single board to see and steer it all.
- People who want to stay the human in the loop: see who's doing what, unblock fast, and keep git honest underneath.
What we believe
- Local-first. Your code, your machine. We don't upload your repo to ship a feature.
- Boring infrastructure. macOS apps, signed and notarized, that just work. No browser, no Electron, no plugins to install.
- Buy once, own forever. Paid features are clearly scoped. The free tier stays useful, see pricing.
Talk to us
Email [email protected] . That goes to a real person, usually within one business day. For longer threads, see contact.