agentic-flow v2.1.3 — Windows fix, cleaner local model routing, jujutsu compatibility
What is agentic-flow?
agentic-flow lets you run Claude Code (or the Claude Agent SDK) against cheaper or fully local AI models instead of always paying for the most expensive one, and then take whatever agent you built and deploy it as a real hosted service. It bundles a router that picks the right model for the job, a memory system (AgentDB) so agents remember what they've learned, and a set of provider integrations (OpenRouter, Ollama, local ONNX models, and more) so you're not locked into one vendor.
What's in this release
This is a patch release — a cleanup pass that closed out a backlog of pull requests, fixed one real Windows crash, and shipped a handful of small, well-verified bug fixes. Nothing here changes how you use agentic-flow; everything is either invisible (a bug you'd only hit in specific conditions) or additive (new example code, a security policy document).
🪟 Fixed a Windows-only crash in local model loading
If you were running agentic-flow's local ONNX inference path on Windows, importing certain modules could crash immediately — even in code paths that never actually used ONNX at all — because the native binding was being loaded as a side effect of just importing the file, and that native binding can't load on some Windows setups. It's now loaded lazily, only when you actually try to run a local model. We verified this fix empirically (not just by reading the code): we reproduced the exact crash-on-import behavior, confirmed the fix removes it, and confirmed the model still loads correctly the moment it's actually needed.
🧵 Fixed a startup crash on newer Node.js
agentdb-cli.ts used a variable (__dirname) that isn't available in modern JavaScript modules, causing it to crash at startup in some environments. Fixed to use the standard modern equivalent.
🔧 jj (Jujutsu) version control support brought up to date
If you use agentic-flow's Jujutsu integration, branch operations (create/delete/list) now use the current jj bookmark command instead of the old jj branch command, which newer versions of Jujutsu (0.21+) removed entirely. Also added the missing macOS Apple Silicon (arm64) build of the Jujutsu bindings, so installs on Apple Silicon Macs no longer silently fall back to an unoptimized path.
🔌 Fully local, no-API-key setup is more reliable
If you run agentic-flow entirely offline against a local model (no cloud API key at all), several small threading issues in how the proxy port, the Ollama provider, and local model file paths were passed around are now fixed — this path should now "just work" more consistently.
📚 32 new example applications
Added a large batch of example projects demonstrating agentic-flow in more advanced scenarios (protein-folding consensus, Byzantine fault-tolerant coordination, peer-to-peer game content generation, and more) — useful as starting points if you're building something ambitious.
🔐 Added a SECURITY.md
A starting point for how to report security issues in this project.
Behind the scenes
We also did a broader cleanup of the project's pull request backlog — closing out several PRs whose underlying bugs had already been fixed a different way elsewhere, a couple that turned out to be unrelated content mistakenly opened against this repo, and one that didn't hold up to a live fact-check. The full reasoning for every decision is documented in ADR-078, and one unrelated-but-real finding (a security gap in an in-progress OAuth feature over in the RuVector project) was flagged there for its author to fix before merging.
We also found and filed a real bug in npm itself that currently blocks the standard npm audit fix command from running in this project — tracked for whoever picks it up next.
Upgrading
npm install agentic-flow@latest
# or, if you use npx:
npx agentic-flow@latest --version # should print 2.1.3No action needed — every change above is either invisible unless you were hitting the specific bug, or purely additive.
🤖 Generated with RuFlo