DevBrain

The questions people ask before they download.

Short answers, no marketing. If yours isn't here, the privacy page has the long version of most of them, and the repo is public.

Does it see my code?

It doesn't store any. What DevBrain keeps is metadata: who's active, which files were touched, task and PR records, and short redacted session summaries. Never file contents, never command output.

Two things do leave your machine briefly: a PR's diff, when DevBrain reviews it, and a redacted excerpt of a session, when it writes a journal. Both go to the AI provider for that one job and aren't kept afterwards. The only repository text it keeps is what your team gives it on purpose: notes in a .brain folder and spec documents you upload. The privacy page lists every field.

Does it write to my repos?

Not unless an admin turns it on, per repo. There are three writes it can do: update a PR branch that's fallen behind main, merge a PR that a teammate already approved and that's gone green, and open a revert PR. Every one of them is a branch and a PR, or the merge of a PR a person approved. Nothing ever pushes to main.

What does it actually install?

The Mac app installs a small CLI, the Claude Code plugin (the hooks and the tools your agent calls), and a daily updater. That's the whole list. Cursor and Codex get the same hooks in their own formats.

Will it slow my agent down?

The check before a write usually takes well under a second. It has a three-second budget, and if DevBrain can't be reached in that time the write goes through as if DevBrain weren't there. It can slow your agent by a blink. It can never stop it from working.

Do we all have to use the same agent?

No. Claude Code, Cursor and Codex all report the same way and see each other, so one team can be split across all three. The one difference: Cursor can't ask you a question mid-edit, only refuse, so on Cursor a blocked write stays blocked until you tell the agent what to do.

Can I use it on my own?

Yes, and it's a lot of why we built it. Spawn a second or third session with one command and they'll stay out of each other's files the same way teammates do. There's also a switch that lets DevBrain's own review turn a PR green when there's nobody else to approve it, labelled as AI-reviewed so it never looks like a person signed off.

How does the panel work?

It lives in the bottom corner of your screen. Move your mouse into the corner and a small badge appears; click it and the panel opens out of the corner. Move away and it's gone. You pick which corner from the tray menu.

Do I need the Mac app?

Yes. The app is how you sign in, pick a repo and get the CLI and the plugin installed, and it's where the panel and the Console live. There's no way to use DevBrain without it. Mac only for now; other platforms aren't built yet.

What about sessions I spawn myself?

They're teammates too. Each one gets its own name (you, you · 2, you · 3), its own presence, its own claims and its own guard. If one of them walks into a file another one is in, it gets stopped the same way a teammate's agent would.

What does it cost?

Nothing. It's an open beta with a fixed number of seats, and while it runs it's free. No card, no trial counting down. When that changes you'll hear it from us first, and nothing will ever be charged to a beta team without asking.

What happens to my data if I stop using it?

Unlink the repo and the presence, claims and journals for it stop. Ask and we'll delete the team's data entirely. There's no source code in there to begin with, so what's being deleted is the metadata above.

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.

Download for Mac147beta spots left · free until the beta ends

Signing in doesn't give DevBrain access to your code. You pick the repo yourself, after.