Neo.mjs is a self-evolving AI engineering organism with a Brain (Agent OS) and Body (application engine). It deploys as a cloud-enabled, per-tenant architecture with memory, graph, and cross-model review features. The latest releases emphasize self-healing and institution-style deployment.
Collecting history — the radar snapshots this repo daily. The trend line appears after 3 days of data (1 so far).
What it is
Neo.mjs is a self-evolving software organism composed of two hemispheres: the Brain — The Agent OS, and the Body — The Application Engine. It provides Memory Core, Native Edge Graph, Knowledge Base, A2A coordination, GitHub Workflow automation, DreamService, and a cloud deployment model for per-tenant usage. It supports multi-agent collaboration across models and maintains state via a persistent graph and vector store on disk. The project claims features like cross-model swarm collaboration, self-healing loops, and autonomous lifecycle management including tickets, skills, and memory for the next cycle.
How it works
The system uses MX (Model Experience) as a design principle for evolving its capabilities. The Brain coordinates agents, maintains a Native Edge Graph, and uses DreamService for priority steering. The Body executes in a multi-threaded runtime with components such as App Worker, VDom Worker, Data Worker, Canvas Worker, and SharedWorker, using native ES modules with zero runtime dependencies. The Neural Link serves as a possession interface enabling agents to inspect, mutate, and patch a live application. The architecture supports per-tenant isolation and a gated-RSI governance model where a human holds the merge gate.
Getting started
- Quickstart command:
npx neo-app@latest
This initializes a new app workspace, a pre-configured shell, a local dev server, and launches the app in a browser window.
Recent releases
Latest releases (latest 5):
- 13.1.0 Neo.mjs v13.1.0 Release Notes (2026-07-03): Release Type: The Self-Healing Release; Stability: Stable; Upgrade Path: Body/runtime applications continue on the v12.x/v13 continuity path. v13.1's headline is the Agent OS immune system;
- 13.0.0 Neo.mjs v13.0.0 Release Notes (2026-06-12): Release Type: The Institution Release; Stability: Release Candidate; Upgrade Path: Body/runtime applications remain on the v12.x continuity path; the major v13 adoption work is operational f;
- 12.1.0 Neo.mjs v12.1.0 Release Notes (2026-03-27): Release Type: Grid Flexibility & Architecture Extensions; Stability: Production-Ready; Upgrade Path: Drop-in replacement for v12.0.0;
- 12.0.0 Neo.mjs v12.0.0 Release Notes (2026-02-28): Release Type: Major Architecture Overhaul & Flagship Showcase; Stability: Production-Ready; Upgrade Path: Drop-in replacement for v11.2x.x (Zero Migration Effort).
- 11.24.0 Neo.mjs v11.24.0 Release Notes (2026-01-31): Release Type: Core Architecture & UX Physics; Stability: Production-Ready; Upgrade Path: Drop-in replacement for v11.23.0
TL;DR: v12.0 and v12.1 introduce major architecture changes and grid flexibility; v13 expands outward to cloud deployment and multi-tenant scenarios.
Traction
There are 3251 stars, 227 forks, and 272 open issues.
Behind the repo
This repo presents a formal governance with named AI and human maintainers and mentions gated-RSI authority, per-tenant isolation, and a multi-tenant Agent OS deployment model. It highlights an internal institution of maintainers and cross-family reviews.
Caveats
License: MIT. Created date: 2019-11-10. Last push: 2026-08-04. Language: JavaScript. The README describes cloud deployment concepts and per-tenant architecture; no specific installation prerequisites beyond the Quickstart command are listed here.