Hold Devin's autonomous work to one merge standard
Devin runs autonomous sessions from AGENTS.md, Knowledge, and Playbooks, and can open pull requests across several repositories at once. Durable requirements end up split between repo files and instructions held inside Devin's Knowledge and Playbooks. Baz enforces the repo-held guidance, connects through MCP so Devin can verify dependencies before it opens a Change, and holds every cross-repo PR to the same merge standard as human-written code.
Devin tells the agent how to work. Baz keeps the standard.
Native customization tells an agent how to work. Baz turns the durable guidance already stored with your code into scoped requirements it can verify on every Change.
Native customization
AGENTS.md, repo Skills, Knowledge, Playbooks, hooks, subagents, and MCP
Where instructions drift
Requirements split between repo-held AGENTS.md and Devin's Knowledge and Playbooks, so a rule that lives only inside Devin is invisible to every other agent and reviewer.
What Baz adds
Baz enforces repo-held AGENTS.md and Skills. Teams can move durable requirements out of Knowledge or Playbooks into versioned repo guidance so every agent and reviewer works from the same contract.
A plan Devin can defend
Devin connects to Baz through MCP. It can use Baz search to verify dependencies and consumers before it opens a Change.
Connect the Baz MCP endpoint to Devin.
Keep durable planning instructions in repo-held AGENTS.md and Skills.
Devin uses Baz search to find relevant repositories, symbols, and files before implementation.
Baz independently reviews the resulting Change against the same standard.
Result Broader planning context for Devin through MCP, followed by the same Baz review and merge standard.
Availability The packaged plan capture workflow is deepest today in Claude Code, Codex, and Cursor. Devin connects through the Baz MCP endpoint and repo-held guidance, while Baz independently reviews the resulting Change.
One independent merge standard
Devin can produce work many ways: Autonomous sessions, Knowledge, Playbooks, repo Skills, hooks, subagents, and MCP. Baz reviews the result after the code exists and decides one thing: Whether the resulting Change follows versioned repo guidance and meets the same merge standard as every other Change.
| Baz capability | Evidence used | Decision supported |
|---|---|---|
| AI Coding Guidelines | AGENTS.md, CLAUDE.md, Cursor rules, and Skills matched to changed paths | Did the agent follow the team's durable instructions? |
| Spec Reviewer | The approved requirements and the resulting implementation | Did the agent build what the team asked for? |
| Checks | CI failures mapped to the relevant files and lines | Does the Change pass the tests and checks that matter? |
| Usage and impact | Services, APIs, consumers, entry points, and runtime context | What could the Change affect beyond the edited files? |
| Advanced Security | Code, dependencies, vulnerability patterns, and adversarial review | Does the Change introduce a security risk? |
| Merger | Findings, discussions, approvals, checks, and team merge requirements | Is the Change ready to merge, blocked, or waiting for a human decision? |
Keep every agent’s strengths. Add one control layer.
Each agent keeps its own way to shape behavior. Baz adds the same evidence before code and the same independent verdict after, so the toolchain can change without resetting the standard.
| Capability | Claude Code | OpenAI Codex | Cursor | Devin |
|---|---|---|---|---|
| Durable repo guidance | CLAUDE.md, imported AGENTS.md, .claude/rules | AGENTS.md | Project Rules, AGENTS.md | AGENTS.md |
| Reusable workflows | Skills and plugins | Skills and plugins | Skills and plugins | Skills and Playbooks |
| Specialized workers | Subagents | Subagents | Subagents | Subagents |
| Tool connections | MCP and plugin-bundled | MCP and plugin-bundled | MCP and plugin-bundled | MCP |
| Baz before code | Packaged Planner plugin and plan capture | Packaged Planner plugin and plan capture | Baz Rule, MCP, and plan capture | Baz MCP with repo-held guidance |
| Baz after code | Independent review and merge verdict | Independent review and merge verdict | Independent review and merge verdict | Independent review and merge verdict |
One control layer, whichever agent your team picks
Claude Code
Baz discovers CLAUDE.md, its @-imported files, .claude/rules, and Skills, then loads only the rules relevant to the changed paths and verifies the Change against them.
Baz + Claude CodeOpenAI Codex
Baz discovers AGENTS.md and Skills, then applies the matching requirements during an independent review in GitHub, outside the session that produced the code.
Baz + OpenAI CodexCursor
Baz discovers repo-held .cursor/rules, AGENTS.md, and Skills, scopes them to the changed paths, and verifies the result outside the editor.
Baz + CursorQuestions teams ask first
What does Devin support today?
Devin connects to Baz through MCP and uses repo-held AGENTS.md and Skills. The packaged plan capture flow currently targets Claude Code, Codex, and Cursor, while Baz reviews every Devin Change independently.
How do we move requirements out of Knowledge and Playbooks?
Store durable requirements as versioned repo guidance. Baz reads it, applies the relevant parts during review, and keeps one contract that every agent and reviewer shares.
Can teams keep human approval for sensitive code?
Yes. Teams can retain explicit human approval for high-risk Changes while Baz reduces repetitive review work on lower-risk ones.
Let developers keep Devin. Keep one standard for the code.
Connect Baz to your repositories and turn the guidance you already maintain into requirements verified on every Change, before code and again before merge.