The questions people ask before they download.

It doesn't copy your repository's files. DevBrain keeps information about the work: who's active, which files were touched, task and PR records, decisions and notes.

With running context on (both setup choices turn it on), the messages you write to your agent and its replies are sent to DevBrain with secrets removed, kept for 30 days, and summarised by the AI provider into session summaries your team keeps. They can include code or command output that was written into the conversation. A PR's diff is sent to the AI provider when DevBrain reviews it, and DevBrain doesn't store it. Apart from that, 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.

Not unless an admin turns it on, per repo. There are four writes: update a PR branch that's fallen behind main, merge a PR (a person clicks Merge once GitHub reports it ready, for teammates' and bots' PRs; or, if an admin chooses that, DevBrain merges a teammate's PR automatically once GitHub reports it ready and its AI review cleared it), open a revert PR, and resolve conflicts that are only inside .brain notes. Your branch protection still applies, and nothing pushes to main.

The Mac app installs a small CLI, the Claude Code plugin (the hooks and the tools your agent calls), a daily updater, and one line in your shell profile so the CLI is on your path. Cursor and Codex get the same hooks, plus DevBrain's tools, in their own config files.

The check before a write is quick. If DevBrain can't be reached within three seconds, the edit goes ahead as if DevBrain weren't there. It can slow your agent by a blink. It can never stop it from working.

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. Codex asks you to approve DevBrain's hooks once, and session capture is fullest on Claude Code.

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.

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.

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. It needs an Apple Silicon Mac (M1 or later, sold since late 2020); Intel Macs and other platforms aren't built yet.

First check the Mac: DevBrain needs an Apple Silicon Mac (M1 or later) on macOS 12 or later. If the DMG didn't download, Safari asks once whether to allow downloads from getdevbrain.com; allow it and download again. If the app isn't in the menu bar, remember it has no Dock icon: move your mouse into the bottom corner of the screen and click the brain, or press Alt+Space. To start over, paste curl -fsSL https://getdevbrain.com/install.sh | sh in Terminal. It reinstalls the app and keeps your sign-in. Still stuck? Write to team@getdevbrain.com.

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.

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. You'll get at least two weeks' notice before it ends. After that, DevBrain only works for teams on a paid plan: a team that hasn't subscribed loses access, and its data is deleted 30 days after the beta ends. Nothing is ever charged to a beta team without it choosing a plan.

Turn off Launch at login in the menu-bar icon and quit DevBrain, but leave the app in Applications for now: the commands below use it. Then run these in Terminal: devbrain hosts remove all (takes DevBrain out of Cursor and Codex), claude plugin uninstall devbrain@devbrain and claude plugin marketplace remove devbrain (the Claude Code plugin), launchctl unload ~/Library/LaunchAgents/com.devbrain.update.plist then rm ~/Library/LaunchAgents/com.devbrain.update.plist (the daily update job), and rm -rf ~/.devbrain (the command-line tool and its settings). Delete the line ending in # devbrain from ~/.zshrc (or ~/.bash_profile). Last, drag DevBrain from Applications to the Bin.

That removes DevBrain from your Mac (a few small app settings files may remain in your Library folder). Your team's data on our side stays until the team is deleted; the next answer covers that.

Unlink the repo and everything for it stops. A team owner can delete the team and all its data from the Console, or ask us to. Deleted data can stay in backups for up to 7 days.