opencode-council
v0.6.2
Published
AI agents that debate before they act. Multi-agent orchestration for OpenCode with governance, heartbeat deliberation, and delegation.
Downloads
381
Maintainers
Readme
OpenCode Council
AI agents that debate before they act.
Multi-agent orchestration for OpenCode where specialized roles deliberate, challenge assumptions, and synthesize recommendations -- instead of blindly executing tasks.
Quick Start
npx opencode-council initOr without Node.js:
curl -fsSL https://raw.githubusercontent.com/marcel-tuinstra/opencode-council/main/install.sh | bashRestart OpenCode, then try:
@cto @dev @pm Investigate why API latency regressed this week and propose a fix plan using sentry and github.What You Get
| Capability | What it does |
|---|---|
| Mention-driven roles | @cto @dev @pm activates the agents you need |
| Heartbeat phases | Frame, Challenge, Synthesize -- structured reasoning for 3+ roles |
| Delegation mode | @cto delegate [prompt] -- lead agent plans and coordinates specialists |
| MCP gating | Sentry, GitHub, Shortcut only activate when explicitly mentioned |
| Governance | Budget limits, reason codes, and policy profiles |
| 10 agents | CTO, CEO, PO, PM, DEV, FE, BE, UX, Research, Marketing (personas) |
Stable Contract
Starting in v0.5.0, the package root intentionally exposes a small stable runtime contract for consumers that build on the live orchestration plugin. The canonical compatibility and deprecation policy lives in docs/guides/compatibility-and-deprecations.md.
That document defines the stable root exports, CLI compatibility, documented env var and policy-key guarantees, and the deprecation/removal process for v0.5.x.
Supervisor helpers and other pre-v0.6.0 orchestration internals remain available under an experimental supervisor entry point instead of the root barrel.
Example
[1] CTO: We need to isolate whether this is compute saturation, query contention,
or an external dependency regression; start with p95/p99 breakdown and release
correlation.
[2] DEV: I will inspect Sentry trace waterfalls for the hottest endpoint and map
spans to the last two deployment windows.
[3] PM: I will prepare a rollback threshold, owner checklist, and a 48-hour
mitigation timeline.
[4] CTO: Recommendation: run a short Sentry trace audit plus GitHub change diff
first, then commit to either rollback or targeted fix.CTO frames the problem, DEV and PM challenge with their expertise, CTO synthesizes. That's the heartbeat model.
Manage Your Install
npx opencode-council refresh # Update to latest version
npx opencode-council verify # Check install health
npx opencode-council uninstall # Clean removalRoadmap
Now (v0.5.0): Deliberative orchestration, delegation mode, MCP gating, budget governance, 10 agent personas, one-command install, and a defined compatibility policy for the stable runtime contract.
Next: Governed parallel execution (supervisor mode) and async delegation with governance.
Documentation
| | | |---|---| | Getting started | Install / Quick start | | Upgrading | Upgrade to v0.5.0 | | Compatibility | Compatibility and deprecations | | Configuration | Customization / Policy profiles | | Architecture | Overview / Positioning | | Troubleshooting | Local sync and agents | | Testing | Guide / Role sanity |
Contributing
npm install && npm test197 tests, CI on every PR. See the testing guide for conventions.
Contact
marcel.tuinstra.dev / [email protected]
License
MIT. See LICENSE.
Independent community plugin for OpenCode. Not affiliated with or endorsed by the OpenCode project.
