Turn one goal into a crew of agents.
Branchlanes plans dependent tasks and runs each with an agent in its own sandbox, on your model keys. Tests gate every change that lands.
Join the waitlistHow it works
You describe a goal. Branchlanes turns it into a plan of tasks that depend on each other, and a crew of agents works through them.
- Goal
- Plan
- Tasks
- Crew
- Landed changes
The crew runs agents in parallel, but never on tasks that touch the same files. By default three agents run at once. Branchlanes is used to build Branchlanes: its own goals land tasks in its own repository.
Your keys, your bill
You bring your own model provider keys. They are stored encrypted and are never sent into the sandbox. You pay your model provider directly; we never mark up tokens.
Sandbox isolation
Every run gets its own sandbox. Inside it there is only a proxy URL and a short-lived token for that run, never your provider key.
Tests gate what lands
Finished tasks wait in a queue. A gate status must pass before anything lands on your main branch.
Spend control
Set a spending cap for each goal when you create it. Per-user daily spend counters keep a runaway crew from running up your bill.
Join the waitlist
We will email you once when Branchlanes (formerly Flook) opens; nothing else.