MindForge

An agentic intelligence framework for Claude Code — orchestrates multi-agent workflows with governance, memory, and autonomous execution. Production-hardened with true parallelism, streaming SDK, and zero-trust security. Install once, get structured AI-driven development with built-in quality gates.

Latest release

v11.9.5 (2026-08-22) — The release path can no longer strand itself, and the SDK ships. 11.9.4 published two packages and then failed on the third; because that step sat before the release page and the stable dist-tag move, its failure skipped both. Fixed two ways: the steps that finish a release now run ahead of any additive package publish, and a new offline preflight gate refuses to reach a publish that the registry will reject. Verified against a worktree at tag v11.9.4 — the exact tree npm rejected — the gate exits 1 and names the file.

mindforge-sdk publishes for the first time since 11.8.0, and for the first time with provenance. Everything fixed in it across 11.8.1–11.9.4 had reached nobody, including a WebSocketEventStream reconnect whose unhandled rejection terminates the caller's process.

The previous release, v11.9.4, is where the hook gates started actually registering: 11.9.3 shipped the code and then declined to run it on essentially every project. Measured against the published tarballs — 11.9.3: 11 hook scripts installed, 0 registered; 11.9.4: 8 registered, 3 deny-class verified blocking. That behaviour change under a patch bump still applies — the installer writes .claude/settings.json where it previously declined, merging append-only and backing up first. See the BREAKING section in CHANGELOG.md, or RELEASENOTES.md for human-readable notes.

What is actually enforced

Read this before the install instructions. MindForge ships a large corpus of agent instructions — commands, skills, personas, protocols — and those are advisory: they work by being in the model's context, and a model can decline them. The parts that would block an action are hooks. Through 11.9.2 no channel registered them. 11.9.3 added the registration code but it declined to run on almost every project, so in practice nothing was enforced there either. As of 11.9.4 both channels register and execute them on Claude Code, and nowhere else.

What that means, measured rather than asserted:

• The npx channel generates the config it never used to ship. files[] has 49 entries and none of them contains settings, so no settings file is published — instead bin/installer/hook-registration.js writes one at install time, merging append-only into any file you already have. Measured on a confined install: 8 hooks registered into .claude/settings.json, of which the installer's own preflight executed 7 and verified all 3 deny-class hooks returning exit 2 before keeping the file. A preflight failure rolls the registration back rather than leaving a config whose commands do not run.
• The plugin channel's dispatcher runs. It previously crashed on every fire — run-with-flags.js requires ./lib/hook-flags and plugins/mindforge/scripts/lib/ was not copied in. That directory now exists, all 14 path tokens in plugins/mindforge/hooks/hooks.json resolve under the plugin root, and driving the dispatcher by hand returns exit 2 for mindforge-block-no-verify and mindforge-config-protection.

Still not enforced, deliberately and with a printed reason for each: any runtime other than Claude Code (Cursor, Copilot, Gemini/Antigravity, OpenCod

... View full README on GitHub