Bisectable is a shared workspace for Codex and Claude Code. It sends each question to the right person and keeps every answer on record.
Bob’s phone5G
10:42
Tuesday 13 October
Bisectablenow
Claude Code asks you
Round partial months to the day, or to the whole month?
Alice’s session · Set a monthly spending cap
You answered: To the day
Dave is reading the recordNo status update needed
Agents
Machines
Connects to
That engineer forwards each question, copies work between sessions and writes the status updates. Every engineer runs many agents, so this never stops.
6messages Alice relayed by hand
Your agents work as they do today. Now the whole team can reach them.
Example: Bob’s Home lists a question from Claude Code in Alice’s session. Bob chooses To the day, and the agent thanks Bob and continues.
Example: two decisions in Codex’s plan for partial refunds change billing/, so they go to Bob. Bob accepts one and overrides the other with a note. The set is complete, and Codex updates the plan.
Example: Alice and Carol both write to Claude Code on devbox-1, a team machine. The agent uses MoneyInput because Carol asked for it.
Example: Alice mentions the review session. The message quotes its three findings, and Claude Code says that it will fix all three.
Example: Dave reads the record of the spending cap. It shows the agent’s summary, who asked, decided and answered, the agents’ work, one CI failure and $6.48 of spend on the Usage-based billing project.
Example: the billing test fails. Bisectable sends the failure to Claude Code, the agent pushes a fix, every job passes and the merge waits for Alice.
Codex and Claude Code run as you set them up today, on your own machines.
1
Run bisectable connect on a Mac, a Linux server or a Coder workspace. It connects out, so you open no ports.
2
Choose a machine, a folder and an agent. Your agents keep their accounts, settings and skills.
3
Teammates see the session on their Home. They can answer the agent, write to it and review its work.
The team can read new sessions unless the owner keeps one private. On team machines, members can write too. On a laptop, only the owner writes, unless they let someone in for a set time.
Code, prompts and conversations stay on your machines. Anything that crosses our service is encrypted for your team’s devices. The service reads only status, timing and names your forge already has.
On Bob’s laptop
Set a monthly spending cap
GitHub · acme/api · PR #612 · CI passed
On Bisectable’s service
Encrypted session title
GitHub · acme/api · PR #612 · CI passedreadable
An active developer owns a session in which an agent ran that month. Invites are free until then. Viewers, reviewers, approvers and managers are never charged.
There is no charge for sessions, agents, machines, repositories, tokens or agent time. Use your own agent accounts. We add no markup to model-provider costs.
Plans start at launch. The private preview is free.
$0For one person hosted.
$25For each active developer, each month.
30-day trial for teams, with no card.
$45For each active developer, each month, billed annually. From 20 developers.
Talk to us about your requirements.
30-day trial.
Annual billing commits and prepays a developer count. Extra active developers are added quarterly at the annual rate for the remaining year. A lower count takes effect at renewal.
Most agent workspaces help one engineer watch their own agents. Bisectable is for the team around them. Each question goes to the person who knows the answer, a plan’s decisions go to the people who own the code, and every answer stays on record for later sessions.
An agent asks a question when it cannot go on without an answer, and it waits on that person’s Home. A decision belongs to the work, such as a plan. An agent raises its decisions as one set, people answer them on one sheet, and later sessions read the answers. Agents raise decisions only when your repository’s skills ask them to.
No. Bisectable runs Codex and Claude Code with your own accounts. Your agents use your settings and skills.
Read access lets a teammate follow the session and answer an agent’s question. Write access lets them send work to the agent. Approve access separately lets a person answer permission requests and approve a merge. Managers read shared sessions, but cannot write or approve.
On your own machine, only you write unless you give a person write access for a set time. On a team machine, a member who can read the session can write. Each message shows who wrote it.
No. The message uses the session’s machine and credentials. The agent gains no authority from the writer’s role. A person still needs Approve access to answer a permission request or approve a merge.
Yes. New organizations let the team read new sessions by default. You can keep a session private. Your organization can also make new sessions visible only to the person who starts them. A private session stays out of the team’s shared lists.
No. Your devices seal code, diffs, prompts and conversations before they reach our servers. The service cannot read that content. It can read operational metadata, such as repository names, branch names and delivery status.
Yes. The source is Apache-2.0, and any team can host Bisectable for free. Enterprise adds organization policy, provisioning and governance.
The private preview is for teams that already use coding agents every day. It is free until launch.