Doramagic.ai Chinese

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.

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?

01

Quick decision

Use this section to decide whether the project is worth a deeper read.
Best forUsers who want source-backed project understanding before installing it.

Match the project to your task before installing it.

Capabilityskill, recipe, host_instruction, eval, preflight

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.

Repositoryneomjs/neo

3.2k stars · 214 forks

02

What it can do

Translate the upstream project into concrete capabilities the user can judge before installing.
1

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
2

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
3

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
4

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
5

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.
Stars3.2k stars
Forks214 forks
Contributors77 contributors
Licenseunknown

Community Discussion Evidence

12 source-linked items

Review 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.

04

How to start

Only source-backed commands are shown here. Verify them in an isolated environment first.
1

Try the prompt first

Test the workflow without installing the upstream project.

preview
2

Read the Human Manual

Understand inputs, outputs, limits, and failure modes.

manual
3

Take context to your AI host

Use the compiled assets in your preferred AI environment.

context
4

Run sandbox verification

Confirm install commands and rollback before using a primary environment.

verify
npm install neo.mjs

Official 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
  1. https://github.com/neomjs/neo Project Manual
  2. Table of Contents
  3. Introduction and Two-Hemisphere Architecture
  4. Related Pages
  5. Overview and Purpose
  6. The Body Hemisphere: Rendering Engine
  7. Off-Main-Thread Component Model
  8. Multi-Worker Coordination
1

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
2

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
3

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
4

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
5

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.

08

Pitfall Log and verification risks

Doramagic surfaces high-risk items before users treat a candidate capability as verified.
high

Installation risk requires verification

May increase setup, validation, or first-run risk for the user.

high

Installation risk requires verification

May increase setup, validation, or first-run risk for the user.

high

Configuration risk requires verification

May increase setup, validation, or first-run risk for the user.

high

Security or permission risk requires verification

May increase setup, validation, or first-run risk for the user.

high

Security or permission risk requires verification

May increase setup, validation, or first-run risk for the user.

high

Security or permission risk requires verification

May increase setup, validation, or first-run risk for the user.

high

Security or permission risk requires verification

May increase setup, validation, or first-run risk for the user.

high

Security or permission risk requires verification

May increase setup, validation, or first-run risk for the user.