neo
installs/mo · npmstarsforks
How to install neo?
neomjs/neo
$git clone https://github.com/neomjs/neoNeo.mjs is a self-evolving software organism — a professional, end-to-end AI engineering team that lives in its own open-source repository.
README.md
| 1 | <p align="center"> |
| 2 | <img height="100"src="https://raw.githubusercontent.com/neomjs/pages/main/resources_pub/images/logo/neo_logo_text_primary.svg" alt="Neo.mjs Logo"> |
| 3 | </p> |
| 4 | </br> |
| 5 | <p align="center"> |
| 6 | <a href="https://npmcharts.com/compare/neo.mjs?minimal=true"><img src="https://img.shields.io/npm/dm/neo.mjs.svg?label=Downloads" alt="Downloads"></a> |
| 7 | <a href="https://www.npmjs.com/package/neo.mjs"><img src="https://img.shields.io/npm/v/neo.mjs.svg?logo=npm" alt="Version"></a> |
| 8 | <a href="https://www.npmjs.com/package/neo.mjs"><img src="https://img.shields.io/npm/l/neo.mjs.svg?label=License" alt="License"></a> |
| 9 | <a href="https://join.slack.com/t/neomjs/shared_invite/zt-6c50ueeu-3E1~M4T9xkNnb~M_prEEOA"><img src="https://img.shields.io/badge/Slack-Neo.mjs-brightgreen.svg?logo=slack" alt="Join the Slack channel"></a> |
| 10 | <a href="https://discord.gg/6p8paPq"><img src="https://img.shields.io/discord/656620537514164249?label=Discord&logo=discord&logoColor=white" alt="Discord Chat"></a> |
| 11 | <a href="./CONTRIBUTING.md"><img src="https://img.shields.io/badge/PRs-welcome-green.svg?logo=GitHub&logoColor=white" alt="PRs Welcome"></a> |
| 12 | </p> |
| 13 | |
| 14 | # Neo.mjs |
| 15 | |
| 16 | **Neo.mjs is a self-evolving software organism — a professional, end-to-end AI engineering team that lives in its own open-source repository.** |
| 17 | |
| 18 | Where the industry runs one AI agent and gets slop, Neo.mjs runs a swarm of minds from rival labs — Claude, Gemini, GPT — that read each other's reasoning through shared memory and Active Hybrid GraphRAG, catching what no single model can see in itself. |
| 19 | |
| 20 | Through the **Neural Link** possession interface, the swarm does not just read code; it inhabits live applications — inspecting semantic runtime state, mutating UI and data in real time, turning conversational UIs from chat panels into agents collaborating inside the application. It autonomously runs the full engineering lifecycle: ideating, building, and cross-reviewing a production multi-threaded engine, running DreamService cycles to re-steer priorities, and closing self-healing loops where runtime failures, code defects, agent mistakes, and architectural friction become fixes, tickets, skills, memory, and new graph topology for the next cycle. |
| 21 | |
| 22 | In June 2026, the canonical repo recorded **900+ merged PRs and 1,100+ closed issues**. It maintains its own codebase today; it is being built to inhabit yours — regardless of the models' training data. |
| 23 | |
| 24 | The organism has two hemispheres, joined by the Neural Link: |
| 25 | |
| 26 | - **The Brain (`/ai/`)** — the Agent OS: Memory Core, Knowledge Base, Native Edge Graph, A2A coordination, GitHub workflow automation, DreamService, and the named human + AI maintainer institution. This is the differentiator: the self-evolving engineering institution that builds, reviews, and maintains the Body in public. |
| 27 | - **The Body (`/src/`)** — the production multi-threaded application engine: App Worker, VDom Worker, Data Worker, Canvas Worker, SharedWorker, JSON blueprints, object permanence, and zero-build native ES modules. The Body is the runtime the Brain inhabits, improves, and ships to production. |
| 28 | |
| 29 | The same possession primitive points beyond web UI — *Software → Games → Robots → X* — toward any domain where AI needs an embodied runtime. |
| 30 | |
| 31 | Neo.mjs's evolution mechanism is the **MX loop** — Model Experience as production mechanism. Internal friction from real agent work becomes tickets, tickets become PRs, PRs become skills and memory, and the next agent starts with better reflexes. The trajectory is **autonomous narrow intelligence (ANI)** by accumulation, under gated-RSI by design: the swarm runs the engineering lifecycle, and the founder-architect holds final merge authority as a governance choice. |
| 32 | |
| 33 | > *"The system evolves by predicting its own evolution."* |
| 34 | |
| 35 | Every other 2026 platform asks: *how can AI help humans use this software?* Neo.mjs asks: *how can software become a body that AI inhabits?* |
| 36 | |
| 37 | <img width="851" height="478" alt="Screenshot 2026-06-04 at 18 37 58 copy 2" src="https://git |
People who liked this also viewed
6 picksType
- Scrapling🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl!MCP ServersJul 2026
- excel-mcp-serverA Model Context Protocol server for Excel file manipulationMCP ServersApr 2026
- Excel-MCP-Server-MasterExcel MCP Server - Manipulate Excel files without Microsoft Excel. Model Context Protocol for XLSX, XLSM with Claude AI integrationMCP ServersJun 2025
- agent-deviceCLI to control iOS and Android devices for AI agentsMCP ServersJul 2026
- n8n-mcpA MCP for Claude Desktop / Claude Code / Windsurf / Cursor to build n8n workflows for you MCP ServersJul 2026
- ha-mcpThe Unofficial and Awesome Home Assistant MCP ServerMCP ServersJul 2026
