Get This Tool
Boffin
Pricing
- Model
- Free
Summary
Static repo-level rules in AGENTS.md tell every agent the same thing — which means the agent touching your payment module gets the same context as the one refactoring a utility helper, and neither gets what it actually needs. Boffin fixes that mismatch by routing per-file, per-edit architectural constraints to whatever coding agent is running.
Boffin sits between your codebase and agents like Cursor, Claude Code, or Codex, feeding each edit the specific rules that apply to that file rather than a flat global prompt. The GitHub page describes it as a staff-engineer control layer: it enforces verification steps after code changes and routes constraints designed to protect existing test coverage and API contracts. It ships via npx boffinit, carries an MIT license, and has no hosted API or agent logic of its own — it controls agents, it does not become one. Where it shows limits: if your team needs dynamic rule generation or the constraint set grows complex enough to require its own maintenance cycle, you are now managing a rules system on top of your codebase. Teams that reach that ceiling tend to bake the constraints directly into their CI pipeline instead.
Bottom line: Boffin earns its place when you have a mixed codebase where some files need strict edit gates and others do not — but if every file needs the same guardrails, a single well-maintained AGENTS.md does the same job without the added layer.
Community Performance Report Card
No community ratings yet. Be the first to rate this tool!
Community Benchmarks Community
Sign in to submit a benchmarkNo community benchmarks yet. Be the first to share a real-world data point.
Pros
Sign in to edit- Per-file rule routing rather than a flat global prompt, which means a high-risk payment module gets strict architectural constraints while a utility file gets none — without you manually managing which agent sees what.
- Post-edit verification hooks built into the control layer, so an agent cannot silently break a test or drift an API contract and move on before you catch it.
- Plugin configs ship for Claude, Cursor, Windsurf, Codex, and Kiro, which means you are not rewriting integration logic when your team switches agents or runs more than one in parallel.
- MIT license and npx install with no hosted API, so there is no vendor dependency, no data leaving your environment, and no cost gate between a proof-of-concept and a production deployment.
- Self-hosted by design, which means your codebase and your rules stay on your infrastructure — a requirement for teams operating under data-residency or IP constraints that a SaaS control layer cannot satisfy.
Cons
Sign in to edit- Rule files for each scoped path require active maintenance: when a module is restructured or renamed, the corresponding rules become stale and the agent receives either wrong guidance or nothing. There is no automated sync between your file tree and your rule definitions — that is a manual process, and on a codebase with frequent structural changes, it becomes a recurring coordination cost.
- The tool has no mechanism for generating or updating rules from observed agent behavior; every constraint is hand-authored. Teams whose constraint sets grow beyond a few dozen scoped rules report the rules directory becoming its own engineering artifact — at which point some abandon the layer and encode the same constraints as linter plugins and test fixtures that run in CI regardless of which agent triggered the change.
- There is no API, so any tooling that needs to query or update rules programmatically — a dashboard, a rule-review workflow, an audit log — requires building directly against the file system. Teams that need visibility into which rules fired on which edits have no built-in observability and must instrument this themselves.
Community Reviews
Sign in to write a reviewNo reviews yet. Be the first to share your experience.
About
- Platforms
- Node.js 18+, Cursor, Claude Code, Codex, OpenCode
- API Available
- No
- Self-Hosted
- Yes
- Last Updated
- 2026-07-28T04:17:30.204Z
Best For
Who it's for
- Teams using Cursor, Claude Code, or similar AI coding agents
- Projects requiring per-edit rule routing instead of static repo rules
- Maintaining test suites and API stability in agent-driven changes
What it does well
- Guiding AI agents on file-specific architectural constraints
- Enforcing verification after code edits by agents
- Preserving existing code paths and test coverage during refactors
Integrations
Discussion Community
Sign in to commentNo discussion yet. Sign in to start the conversation.
Compare Boffin
Spotted incorrect or missing data? Join our community of contributors.
Sign Up to ContributeCommunity Notes & Tips Community
Sign in to contributeBe the first to contribute. General notes, observations, gotchas, and tips from people who use this tool day-to-day.
Frequently Asked Questions
- Is Boffin free?
- Yes — Boffin is fully free to use. There is no paid tier.
- Is Boffin open source?
- Yes. Boffin is open source.
- Can I self-host Boffin?
- Yes. Boffin supports self-hosting on your own infrastructure.
- What platforms does Boffin support?
- Boffin is available on: Node.js 18+, Cursor, Claude Code, Codex, OpenCode.
Hours Saved & ROI Stories Community
Sign in to contributeBe the first to contribute. Concrete time/cost savings, with context. e.g. "Cut my code review backlog from 4h to 45m per week."
Curated lists that include this category
Most AI coding agents read one global instruction file and apply it everywhere. Boffin replaces that with a routing layer: it intercepts an agent’s edit intent, matches the target file against a set of architectural rules defined for that path or module, and delivers only the relevant constraints to the agent before the edit happens. After the edit, Boffin can require verification steps — checks that the change did not break a test or drift an API contract — before the agent moves on. The core workflow is install via npx boffinit, define rules scoped to file paths or modules, and let the layer handle delivery to whichever agent your team runs.
The differentiating claim, stated explicitly on the GitHub page, is that this is ‘not another AGENTS.md.’ Where AGENTS.md gives every agent a single flat prompt, Boffin’s per-edit routing means the agent working inside a high-risk module sees rules that agent working on a utility file never receives. The repository includes plugin configs for Claude, Cursor, Windsurf, Codex, and Kiro, and the folder structure shows dedicated rule directories for each — suggesting the routing adapts to agent-specific plugin formats rather than relying on a single universal interface.
Boffin fits teams running AI-assisted refactors on codebases where test coverage and API stability are non-negotiable and where different parts of the repo carry different risk levels. It does not fit teams that want the control layer itself to be an agent — Boffin has no autonomous decision-making; it routes and enforces, nothing more. The constraint: rule maintenance is a real cost. As the number of scoped rules grows, someone owns that file tree, and if that ownership lapses, the layer becomes noise rather than guardrail. Teams that find rule maintenance exceeding the value it delivers typically consolidate back to CI-level enforcement — linters, schema validators, and test gates — and drop the agent-specific layer entirely.