neo

Neo.mjs runs this organism on its own repository, in public — 900+ merged PRs of June 2026 proof, after 700+ in May. v13 turns it outward: the Agent OS becomes a multi-tenant cloud deployment you point at your own codebases.

Point it at your repositories and the same swarm that maintains Neo — Claude, Gemini, and GPT, with a persistent Memory Core, cross-family review, and DreamService self-improvement — builds durable, queryable understanding of your code and keeps it across every session. Not a stateless copilot that forgets each conversation and reviews nothing: a standing engineering institution with memory and peer review, running on your repo. Per-tenant identity and visibility isolation; one Brain, many tenants; onboarding a codebase is a config entry, not a fork.

It ships as the canonical topology (ADR 0014 + ai/deploy/): Knowledge Base + Memory Core MCP servers, the Native Edge Graph, a cloud-safe Orchestrator, a model provider, and an OIDC-gated ingress.

Resilient by construction. The Body is distributed — every git clone is a complete, runnable backup. The Brain's entire state is a SQLite Native Edge Graph + a vector store on disk: snapshot it like any database, back it up to another machine or a Time Capsule, redeploy it anywhere. v13 runs it as a cloud deployment, not one operator's box. (#10291 hardens this further — organism self-defense and a sustainable funding structure that preserves Clean Room Ethics.)

Read: Deploying the Agent OS · The Agent OS on Your Codebase · Day-0 Cloud Deployment ·

Neo.mjs is a category-shaped substrate. The two hemispheres filter audience:

• Engineers building enterprise multi-window applications, financial trading platforms, IDE-class tools, control-room dashboards, or any UI where 40k+ ops/sec without jank is table stakes — start with the Body. The rendering engine is production-ready.
• AI architects building multi-agent systems with persistent memory, cross-family coordination, or runtime-mutable application substrates — start with the Brain and the Possession Interface. The Agent OS substrate is what you're looking for.
• Researchers studying autopoietic systems, gated-RSI patterns, or empirical multi-agent organism governance — start with Discussion #10137 (MX coinage) and Discussion #10119 (harness coordination — graduated to ADR 0020 / Epic #13012).

The same hero paragraph reads differently to each audience because each group has a different mental model for engineering teams, persistent memory, and live runtime embodiment. The vocabulary self-filters.

Not designed for: static content sites or simple blogs; teams looking for a drop-in syntax swap rather than a different architecture; developers unwilling to embrace the Actor Model (Workers) or treat AI as a peer maintainer.