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	9662
title	Dream Mode Phase 3: GraphRAG Topology & REM Mode Orchestration
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Apr 3, 2026, 4:46 PM
updatedAt	Apr 4, 2026, 2:04 AM
githubUrl	https://github.com/neomjs/neo/issues/9662
author	tobiu
commentsCount	1
parentIssue	9638
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 4, 2026, 2:04 AM

Dream Mode Phase 3: GraphRAG Topology & REM Mode Orchestration

Closed v13.0.0/archive-v13-0-0-chunk-2 enhancementai

tobiu commented on Apr 3, 2026, 4:46 PM

Overview

This ticket encompasses Phase 3 of the Swarm Orchestrator "Dream Mode" epic (#9638). Now that we possess autonomous sub-agent delegation (Browser, Librarian), native MCP tool reflection, and 50-turn memory horizons, we need to implement the overarching cognitive strategies that drive true autonomy.

Objectives

GraphRAG Topology Mapping: Introduce mechanisms for agents to build relationship graphs of the codebase structure (components, mixins, styles). We must move away from flat vector retrieval to traversable dependency maps.
REM Mode (Offline Dreaming): Configure the background loop where an agent can operate completely autonomously when the developer is idle.
- Identify deferred/TODO items in the memory core.
- Autonomously spawn structural tests, format refactoring, or documentation generation.
- Curate new Knowledge Items (KIs) without human prompting.

Acceptance Criteria

Implement GraphRAG topological indexing logic for codebase components.
Create an offline trigger or background scheduling system for REM Mode.
Agent successfully refactors a component or creates tests completely offline, persisting the result to memory.

tobiu added the enhancement label on Apr 3, 2026, 4:46 PM

tobiu added the ai label on Apr 3, 2026, 4:46 PM

tobiu added parent issue #9638 on Apr 3, 2026, 4:46 PM

tobiu assigned to @tobiu on Apr 3, 2026, 4:49 PM

tobiu Apr 4, 2026, 2:04 AM

Superseded by the new architecture roadmap defined in Epic #9671 (specifically #9673 and #9674).

tobiu closed this issue on Apr 4, 2026, 2:04 AM