Match the project to your task before installing it.
Customer Communication & Team Operations · Public
neo
Neo.mjs is a self-evolving software organism: a professional end-to-end AI engineering team whose cross-model swarm inhabits live apps via Neural Link, Active Hybrid GraphRAG, DreamService, and self-healing loops.
Check whether this project matches your task before installing it.
What it can doskill, recipe, host_instruction, eval, preflightReview the portable capability path.
Before continuingVerify in a sandboxDo not treat a preview pack as a proven local install.
GitHub snapshot3.2k stars214 forks · 77 contributors
Doramagic.ai Last verification date: 2026-06-24 Verification method: source evidence, semantic profile, public page gate, and static build acceptance.
Publication status · 2026-06-24
What is neo?
- Neo.mjs is a self-evolving software organism: a professional end-to-end AI engineering team whose cross-model swarm inhabits live apps via Neural Link, Active Hybrid GraphRAG, DreamService, and self-healing loops.
- Best fit: Users who want source-backed project understanding before installing it.
- Not for: Not for users who want to skip sandbox verification or cannot accept configuration, permission, or maintenance overhead.
- Capability added to an AI workflow: skill, recipe, host_instruction, eval, preflight
- First safe verification step: Verify the smallest path in an isolated environment and keep a rollback path.
- Verification state: source, Quick Start, and sandbox install checks are recorded as passed.
- Top risk: May increase setup, validation, or first-run risk for the user.
- Evidence base: https://github.com/neomjs/neo, https://github.com/neomjs/neo#readme, Human Manual, Pitfall Log
01
Quick decision
Use this section to decide whether the project is worth a deeper read.Neo.mjs is a self-evolving software organism: a professional end-to-end AI engineering team whose cross-model swarm inhabits live apps via Neural Link, Active Hybrid GraphRAG, DreamService, and self-healing loops.
3.2k stars · 214 forks
02
What it can do
Translate the upstream project into concrete capabilities the user can judge before installing.Introduction and Two-Hemisphere Architecture
Related topics: The Body - Multi-Threaded Application Engine, The Brain - Agent OS and AI Engineering Team, Getting Started, Workspaces, and Examples
Source: https://github.com/neomjs/neo / Human Manual
The Body - Multi-Threaded Application Engine
Related topics: Introduction and Two-Hemisphere Architecture, The Brain - Agent OS and AI Engineering Team, Getting Started, Workspaces, and Examples
Source: https://github.com/neomjs/neo / Human Manual
The Brain - Agent OS and AI Engineering Team
Related topics: Introduction and Two-Hemisphere Architecture, The Body - Multi-Threaded Application Engine, Getting Started, Workspaces, and Examples
Source: https://github.com/neomjs/neo / Human Manual
Getting Started, Workspaces, and Examples
Related topics: Introduction and Two-Hemisphere Architecture, The Body - Multi-Threaded Application Engine, The Brain - Agent OS and AI Engineering Team
Source: https://github.com/neomjs/neo / Human Manual
Doramagic Pitfall Log
Source-linked risks stay visible on the manual page so the preview does not read like a recommendation.
Source: Doramagic discovery, validation, and Project Pack records
Sources: https://github.com/neomjs/neo, Human Manual, Project Pack evidence, and downstream validation signals.
03
Community Discussion Evidence
Project-level external discussion stays visible on the detail page, not only inside the manual.Community Discussion Evidence
12 source-linked itemsReview these external discussions before using neo with real data or production workflows. They are review inputs, not standalone proof that the project is production-ready.
-
01
Strengthen ADR-19 trigger and lint AiConfig aliases
github / github_issue
-
02
[Epic] Investigation: orchestrator heavy-maintenance runs 14h but the ba
github / github_issue
-
03
[Epic] Daemon-based A2A message ingestion — decouple add_message from th
github / github_issue
-
04
revert: synced content mirrors are real third-party GitHub authorship —
github / github_issue
-
05
feat(ai): symmetric force-refetch for pulls & discussions (refetchPullsB
github / github_issue
-
06
Generic-by-default harness adapter surface — minimize per-family (Claude
github / github_issue
-
07
MX: Stop-hook value-floor — bias the forced next-action toward high-valu
github / github_issue
-
08
[Epic] Orchestrator recovery daemon — reactive heal/act half of self-hea
github / github_issue
-
09
Orchestrator container-health self-healing daemon
github / github_issue
-
10
Prove deployment immune-system closeout via live smoke
github / github_issue
-
11
Accept documented Micro-Delta PR reviews in manage_pr_review
github / github_issue
-
12
src/MicroLoader.mjs: replace the fetch() call with a json module import,
github / github_issue
04
How to start
Only source-backed commands are shown here. Verify them in an isolated environment first.Try the prompt first
Test the workflow without installing the upstream project.
previewRead the Human Manual
Understand inputs, outputs, limits, and failure modes.
manualTake context to your AI host
Use the compiled assets in your preferred AI environment.
contextRun sandbox verification
Confirm install commands and rollback before using a primary environment.
verifynpm install neo.mjsOfficial start command · https://github.com/neomjs/neo#readme · verified: yes
05
Human Manual
The English page must expose the real manual, not a short placeholder.8+ sections · Human Manual
neo Manual
Neo.mjs is a category-shaped JavaScript substrate that combines a production-ready UI rendering engine with an AI-native Agent Operating System. The project describes itself as having a tw...
Open the full manual- https://github.com/neomjs/neo Project Manual
- Table of Contents
- Introduction and Two-Hemisphere Architecture
- Related Pages
- Overview and Purpose
- The Body Hemisphere: Rendering Engine
- Off-Main-Thread Component Model
- Multi-Worker Coordination
Introduction and Two-Hemisphere Architecture
Related topics: The Body - Multi-Threaded Application Engine, The Brain - Agent OS and AI Engineering Team, Getting Started, Workspaces, and Examples
Source: https://github.com/neomjs/neo / Human Manual
The Body - Multi-Threaded Application Engine
Related topics: Introduction and Two-Hemisphere Architecture, The Brain - Agent OS and AI Engineering Team, Getting Started, Workspaces, and Examples
Source: https://github.com/neomjs/neo / Human Manual
The Brain - Agent OS and AI Engineering Team
Related topics: Introduction and Two-Hemisphere Architecture, The Body - Multi-Threaded Application Engine, Getting Started, Workspaces, and Examples
Source: https://github.com/neomjs/neo / Human Manual
Getting Started, Workspaces, and Examples
Related topics: Introduction and Two-Hemisphere Architecture, The Body - Multi-Threaded Application Engine, The Brain - Agent OS and AI Engineering Team
Source: https://github.com/neomjs/neo / Human Manual
Doramagic Pitfall Log
Source-linked risks stay visible on the manual page so the preview does not read like a recommendation.
Source: Doramagic discovery, validation, and Project Pack records
06
AI Context Pack and portable assets
After deciding to continue, take the project context into your own AI host.Complete pack plus user-owned assets
These files are planning and verification assets for Claude Code, Codex, Gemini, Cursor, ChatGPT, and other AI hosts.
07
Preflight checks
Treat this page as a planning asset, not proof that your local environment is ready.- The manual is generated from source-linked project files and Doramagic validation signals.
- Community evidence warnings stay visible instead of being converted into marketing claims.
- This English page is indexable because the locale quality gate passed and explicit English index approval is enabled.
- Use the upstream repository as the final authority for installation commands, license, and version-specific behavior.
08
Pitfall Log and verification risks
Doramagic surfaces high-risk items before users treat a candidate capability as verified.Installation risk requires verification
May increase setup, validation, or first-run risk for the user.
Installation risk requires verification
May increase setup, validation, or first-run risk for the user.
Configuration risk requires verification
May increase setup, validation, or first-run risk for the user.
Security or permission risk requires verification
May increase setup, validation, or first-run risk for the user.
Security or permission risk requires verification
May increase setup, validation, or first-run risk for the user.
Security or permission risk requires verification
May increase setup, validation, or first-run risk for the user.
Security or permission risk requires verification
May increase setup, validation, or first-run risk for the user.
Security or permission risk requires verification
May increase setup, validation, or first-run risk for the user.