What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	7837
title	Cleanup redundant awaits in self-healing example
state	Closed
labels	airefactoring
assignees	tobiu
createdAt	Nov 21, 2025, 10:14 AM
updatedAt	Nov 21, 2025, 10:16 AM
githubUrl	https://github.com/neomjs/neo/issues/7837
author	tobiu
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Nov 21, 2025, 10:16 AM

Cleanup redundant awaits in self-healing example

Closed v11.8.0/archive-v11-8-0-chunk-1 airefactoring

tobiu commented on Nov 21, 2025, 10:14 AM

The ai/examples/self-healing.mjs script currently awaits both LifecycleService and ChromaManager for each service. With the recent refactoring (issue #7836), ChromaManager.ready() is sufficient as it ensures the lifecycle service is ready. This task removes the redundant calls.