Your work should stay yours.

What we believe

Your work should stay yours, no matter who or what you work with. Forkbench is built around clear boundaries, giving you control over how your work is accessed, shared, supervised, and interacted with. Whether it's AI, colleagues, partners, or clients, you can collaborate and share active parts of your work without losing ownership or security.

Why Forkbench?

Coding agents got good enough to run on their own. That is the point of vibe coding, and it is also the problem: an agent running in your shell can reach everything you can, and five of them in five tabs are hard to keep an eye on.

Forkbench puts the lines back. Each job lives in its own Thread. You can lock a Thread to its folders so the macOS kernel keeps its agents out of the rest of your home folder, and give them API keys from the Vault that they use without ever reading. While they work, every tab shows who is busy, who is stuck and which task each one claimed. When a colleague or a client needs in, you share that one Thread, not your laptop, and nothing counts as done until you accept it.

Who we built it for

• Vibe coders who let the agent run and want a boundary it cannot talk its way past.
• Developers running several agents from different vendors, who need to see the whole squad in one window.
• Freelancers and teams who have to let someone else in, a colleague, a partner or a client, without handing over the machine or the keys.

How we build it

• Your code stays on your machine. Repositories, scrollback and shell history never leave it.
• Native and signed. A real desktop app, signed and notarized by Apple on macOS. No Electron, no plugins.
• Free where it counts. Everything that draws the lines on one machine is free. See pricing for what Pro adds.

Talk to us

Email [email protected]. That goes to a real person, usually within one business day. For longer threads, see contact.