A batteries-included CLI that brings conventions to your coding agent workflow.
Your process, knowledge, and constraints live in a Git repo. Every agent picks them up automatically.
This implementation matches the design proposal I created.
Auth middleware added with refresh token rotation. All 12 tests passing.
Looks great. Merging.
feat(auth): implement JWT authentication #43
Push a file at the team, project, or member level. Every relevant agent picks it up. No copy-pasting.
Pick a profile. It stamps out your process, roles, knowledge structure, and defaults. Customize from there.
Scope knowledge and constraints at four levels - team, project, member, and member+project. The right agent sees the right context.
Every decision, every PR, every status change — on your GitHub board.
Your entire team is version-controlled. Clone it, fork it, ship it to another project.
From full approval gates to fully autonomous. You set the guardrails.
Pick a profile, hire agents, launch.
bm init
bm teams sync
bm start
Common questions about BotMinter.
Claude Code is the recommended backend and all shipped profiles are built for it today. Under the hood, BotMinter uses Ralph orchestrator, which also supports Gemini CLI, Codex, Kiro, Amp, Copilot CLI, and OpenCode. Profiles for these backends are planned.
Not at all. It depends on the profile you choose. The agentic-sdlc-minimal profile runs
a single agent that wears multiple hats — planner, implementer, reviewer — all in one.
Other profiles like scrum distribute those hats across specialized agents.
You pick the formation that fits your workflow.
No. BotMinter focuses on conventions, not a specific methodology. It ships with opinionated defaults (like the Scrum profile), but profiles are fully customizable. Think of it like Rails for web or Spring for enterprise — baked-in conventions that you can tweak to fit your process. You can fork an existing profile or create one from scratch.
Get started in minutes. All you need is the bm CLI and a GitHub repo.