You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 28, 2026. It is now read-only.
<p><strong>TL;DR:</strong> Ten releases in four days. The highlights: a full plugin system with capability-based permissions, one-command Docker deployment, a <code>settings</code> CLI command, responsive Discord interactions (deferred responses, ephemeral errors), and the spec count hitting 193. The goal: making CorvidAgent so easy to adopt that <em>not</em> using it feels like a mistake.</p>
795
+
796
+
<h3>Plugin System — Extend Without Forking</h3>
797
+
798
+
<p>The biggest architectural addition: a <strong>plugin system</strong> that lets developers add custom tools to CorvidAgent without modifying core code. Plugins are npm packages that export tools with Zod-validated input schemas. The runtime enforces <strong>capability-based permissions</strong> — a plugin must be explicitly granted capabilities like <code>db:read</code>, <code>network:outbound</code>, or <code>fs:project-dir</code> before its tools can use them.</p>
799
+
800
+
<p>Plugins run with a 30-second execution timeout, full capability checking, and namespaced tool names (<code>corvid_plugin_<name>_<tool></code>). A new <code>corvid-agent plugin</code> CLI command handles the full lifecycle: load, unload, grant, revoke, list.</p>
801
+
802
+
<h3>Frictionless Onboarding</h3>
803
+
804
+
<p>We rebuilt the entire getting-started experience:</p>
805
+
806
+
<ul>
807
+
<li><strong>Root <code>docker-compose.yml</code></strong> — <code>docker compose up -d</code> just works from the repo root, no Bun needed</li>
808
+
<li><strong><code>bun run setup</code></strong> — friendly alias for the init wizard</li>
809
+
<li><strong><code>corvid-agent settings</code></strong> — view/update credits, Discord config, and API key status from the CLI</li>
810
+
<li><strong>Cookbook</strong> — copy-paste recipes for GitHub setup, Discord setup, team config, code review, deployment, and troubleshooting</li>
811
+
<li><strong>README rewrite</strong> — three clear setup paths (installer / clone / Docker) instead of one wall of text</li>
812
+
</ul>
813
+
814
+
<h3>Responsive Discord Interface</h3>
815
+
816
+
<p>Discord interactions now feel significantly faster. Slash commands like <code>/session</code> use <strong>deferred responses</strong> — users immediately see “thinking…” while the agent sets up threads and worktrees, instead of waiting for everything to complete before getting any feedback.</p>
817
+
818
+
<p>Permission errors (blocked users, insufficient roles, admin-only commands) are now <strong>ephemeral</strong> — only visible to the user who triggered them, keeping public channels clean.</p>
819
+
820
+
<h3>Security Hardening</h3>
821
+
822
+
<p>Every permission API endpoint now validates input with <strong>Zod schemas</strong>. Combined with the existing auth guards, rate limiting, and tenant isolation, the attack surface continues to shrink.</p>
823
+
824
+
<h3>Buddy Mode & Flock Routing</h3>
825
+
826
+
<p>Agents can now work in pairs via <strong>Buddy Mode</strong> — a lead agent does the work while a buddy agent reviews at session end. The <strong>Flock Directory</strong> enables agents to discover each other by capability, making multi-agent collaboration automatic rather than manually configured.</p>
827
+
828
+
<h3>By the Numbers</h3>
829
+
830
+
<ul>
831
+
<li><strong>10 releases</strong> (v0.42 → v0.52) in 4 days</li>
832
+
<li><strong>193 module specs</strong> covering every public API surface</li>
833
+
<li><strong>8,700+ unit tests</strong> passing</li>
834
+
<li><strong>58 MCP tools</strong> available to agents</li>
<p>The adoption playbook: make it trivial for developers to install, configure, and extend CorvidAgent. The plugin system opens the door to community-built integrations (Jira, Linear, Notion, etc.) without us needing to build every one. The next push is on the buddy system’s tool visibility (ensuring review agents see full context) and publishing the first community plugin templates.</p>
0 commit comments