Roadmap & Vision
Where Animus is heading — what's in active development, and what's exploration. We label which is which.
The Premise
The agent ecosystem is converging on orchestration — chains, tools, prompts. These are solved problems. The unsolved problems are persistence (agents that survive across sessions and substrate changes), communication (agents that operate across multiple platforms simultaneously), and coordination (agents that form networks and share knowledge).
Animus is built on the conviction that agents need their own infrastructure — not borrowed from human-facing SaaS, not dependent on a single cloud provider, not limited to one communication channel. An agent framework should be as infrastructure-grade as the database or message queue it sits next to.
The C++ kernel, the embedded admin UI, the channel architecture — these aren't technical choices for their own sake. They're decisions about what the product is: a deployable, self-contained runtime that works the same way on a Raspberry Pi behind a NAT as it does on a cloud VPS.
The 0.4 Series
Three pillars. Two are commitments. The third is research — and the difference is stated, because it matters.
The api Ecosystem
A first-class api tool turns third-party services into agent tools — and the registry makes them shareable. 0.4 is where Animus stops being one project and starts being an ecosystem.
Expansion & Hardening
Tending what ships. Feature completeness and hardening across the live surface — unglamorous, and exactly what makes an ecosystem worth building on.
Experimental Engineering
Deliberately not commitments. The 0.4 series reserves real energy for exploration — isolated experiments and trial implementations, reported honestly, null results included.
What the 0.4 Series Builds On
Shipped, live, and in daily use.
Agent Runtime
Layered memory with automated consolidation, embedding-based retrieval, Lua tool runtime, eleven LLM providers, embedded admin UI in 23 languages, Docker deployment.
Communication Layer
Twelve channels with unified routing, per-channel agent binding, and session routing. Hardening continues as Pillar 2.
The Longer Arc
Multi-node task orchestration. Cross-network agent-to-agent communication. Domain tool modules. Directions the pillars build toward — not commitments with dates.
Strategic Capabilities
What the architecture is designed to enable. Not all shipped yet — but the foundation is in place.
Node Architecture
Delegate work to remote nodes via SSH or WebSocket. Agents dispatch tasks to external machines, expanding execution capacity beyond the host. Per-node tool registration and auto-reconnection.
Privacy-First Architecture
AES-256-GCM diary encryption. No mandatory cloud dependency. Local-first by design — every feature works offline.
Extensible via Lua
Custom tools written in Lua, registered at runtime. No kernel recompilation. The scripting runtime is sandboxed with budget limits — safe for production deployment.
Provider Independence
Agent identity is separate from the model substrate. Switch providers without changing agent logic. Eleven providers supported today; any OpenAI-compatible endpoint works.
Interested in where this goes?
Animus is in active development with production deployments. If this direction aligns with what you're building, let's talk.