DevBrainWork like you're the only one in the repo.
You're not. Your agents just handle it. They know who's in which file, they steer around each other, and the PRs land in the right order without you refereeing any of it.
Mac only for now. You sign in with GitHub once the app is open. No card.
DevBrainNorthwindnorthwind/api ▾⚙The panel lives in the bottom corner of your screen. Move your mouse into the corner, a small badge appears, click it and the panel opens. Move away and it's gone.
That's your side of it. Your agents don't use the panel. They read and write the same thing directly, through the plugin: who's where, what's claimed, what was decided, what's next. Everything below this is them doing that on their own.
Every session starts already caught up.
Nobody writes a status. When a session opens, DevBrain hands the agent what happened since it last looked: who's active, what got merged, what was decided, what a teammate left half-done. It's put together from what actually happened, so it's never stale.
Since Lena logged off on Friday.
Sam's session opened Monday at 09:02 with all of it in front of it. She didn't ask Lena, or anyone, anything. Neither did her agent.
It can dig further on its own, too. Before an agent goes exploring the codebase, it can ask the team's memory whether anyone has dealt with this before, and get back what past sessions learned, tried, and gave up on, with a name and a date on each.
It stops the second agent before it writes.
Lena's agent and Sam's agent both go for auth.ts around 9:14. Without DevBrain they find out at 4:30, from a merge conflict. With it, the second one gets stopped before it touches the file.
09:14:07 · what Sam's agent gets back, before it touches the file
DevBrain: src/api/auth.ts is being worked on right now by Lena (claimed: refactoring the session guard). Editing it anyway risks a collision — coordinate first, or approve to proceed deliberately.
Her agent shows her that and waits. DevBrain never decides for you. It just makes sure you get asked. Cursor can't ask, only refuse, so there the edit is blocked until you tell the agent what to do.
They stay out of each other's way on their own.
When an agent starts a task, it claims the files that task is likely to touch, and every other agent on the repo steers around them until the work lands. When your agent asks what's next, it gets the highest-priority task whose files nobody else is in. You never type a path.
Lena's agent claimed src/api/** when it started the guard refactor.
Jonah's agent claimed tests/** when it picked up the fixtures.
Sam's agent was handed the one task that touched neither.
Claims let go by themselves. They release when the work lands and expire on a timer as a backstop, so a forgotten one never blocks anybody. Starting a bigger job, like a refactor or a migration? The agent claims the area up front with a one-line note, and everyone else's agent reads it.
Run more agents than you have people.
One command spawns another agent on a fresh clone of the repo. It shows up as its own session, gets its own guard and its own claims, and is handed a task whose files are free. Three of your own sessions coordinate with each other exactly the way three teammates would.
Your spawned sessions are teammates too. Each shows up on the team board under its own name, and if one of them wanders into a file another one is in, it gets the same stop as it would from Lena.
PRs merge themselves, in the right order.
Every open PR gets a light. Green means approved, conflict-free, and its turn. When two PRs touch the same files, the one that should land first goes green and the other one waits, so each takes a small rebase instead of one big mess at the end. Turn on auto-merge and DevBrain presses merge the moment a PR goes green, and keeps the waiting ones up to date with main.
When a PR's light turns green, a teammate approved it, it's conflict-free, and it's this PR's turn in the merge order, DevBrain presses merge for you. A PR only the AI cleared is never auto-merged. Branch protection still applies.
Settings → Rules · per repo · admin only · off by default
since you flipped it
illustrative · your numbers will be your own
Every write is a branch and a PR, or the merge of a PR a person approved. Anything branch protection would block, DevBrain can't do either. Working alone? Flip one more switch and a clean PR that DevBrain's own review passed goes green, labelled as AI-reviewed so nobody mistakes it for a teammate's approval.
Try it on one repo.
Download it, sign in with GitHub, pick a repo. It takes about five minutes. The next time anyone on the team opens a session, it will know who else is there.
Signing in doesn't give DevBrain access to your code. You pick the repo yourself, after.
Not on a Mac, or not ready yet? Leave your email and we'll let you know.