What is the 'Neural Link'?

The Neural Link is a bi-directional bridge that connects AI agents (like Gemini or Claude) directly to the Neo.mjs runtime. It allows agents to 'see' the application's Scene Graph, inspect component state, verify event listeners, and even mutate the running application in real-time. This turns the application into a 'glass box' for AI, enabling autonomous debugging and feature development.

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

Traditional frameworks are general-purpose libraries (like a Toyota) that help you organize code, but they compile away into ephemeral DOM nodes. Neo.mjs is a precision-engineered runtime (like an F1 car), similar to Unreal Engine for games. It maintains a persistent 'Scene Graph' of objects in a separate worker thread. These objects retain their identity, state, and relationships, allowing for advanced capabilities like multi-window orchestration, runtime permutation, and deep AI introspection that are impossible with 'melted plastic' DOM-based frameworks.

What is 'Context Engineering'?

Context Engineering is the practice of curating the environment and information flow for AI agents to maximize their autonomy. In Neo.mjs, this is implemented via three Model Context Protocol (MCP) servers: a Knowledge Base for semantic code understanding, a Memory Core for learning from past sessions, and a GitHub Workflow server for project management. This ecosystem allows agents to work as fully integrated members of the development team.

What is 'Object Permanence' in the context of Neo.mjs?

In Neo.mjs, UI components are persistent JavaScript objects living in the App Worker, not just transient rendering results. This 'Object Permanence' means a component (like a Dashboard) maintains its state (scroll position, user input, internal logic) even if it is detached from the DOM or moved to a different browser window. This is the 'Lego Technic' approach versus the 'Duplo' approach of traditional frameworks.

What is an 'Agent Operating System'?

Neo.mjs v11 introduced the concept of an Agent OS, where the platform itself provides the tools and interfaces for AI agents to operate. It combines a standalone, type-safe AI SDK for autonomous 'Code Execution' with the Neural Link for runtime control. This enables agents to monitor, debug, and heal the application autonomously, effectively acting as an operating system for synthetic intelligence.

How does Neo.mjs handle multi-window applications?

Neo.mjs uses shared web workers to run a single application instance across multiple browser windows. All windows share the same application state and data in real-time. Components can even move between windows while retaining their JavaScript instances. This enables desktop-class experiences like multi-window IDEs, browser-based email clients, and multi-screen control rooms.

What makes Neo.mjs different from React, Angular, or Vue?

Neo.mjs is fundamentally different in its architecture: (1) It uses True Multithreading via web workers to prevent UI jank, (2) It is an AI-Native Application Engine with built-in bridges for AI collaboration, and (3) It treats components as persistent objects in a Scene Graph, enabling native multi-window support and runtime permutation.

Frontmatter

id	9638
title	Epic: Architecture - Neo.mjs Dream Mode & GraphRAG Swarm
state	Closed
labels	epicaiarchitecture
assignees	tobiu
createdAt	Apr 3, 2026, 12:42 PM
updatedAt	Apr 4, 2026, 2:04 AM
githubUrl	https://github.com/neomjs/neo/issues/9638
author	tobiu
commentsCount	1
parentIssue	9671
subIssues	9639 Local LLM Provider Adapter (Ollama + Gemma-4) 9640 Knowledge Graph Database Backend (Neocortex) 9641 The "Night Shift" REM Pipeline (Hippocampus) 9642 Unified GraphRAG MCP Interface 9643 "Librarian" Sub-Agent Orchestration 9658 Enhance Memory-Core for explicit Gemma4 offline session summarization 9659 Enhance Memory Core with Agent and Model Traceability 9660 Native MCP Tool Execution inside Loop.mjs 9661 Phase 2: Autonomous Sub-Agent Delegation (Dream Mode) 9662 Dream Mode Phase 3: GraphRAG Topology & REM Mode Orchestration 9665 Stabilize MCP Server Infrastructure & Fix Memory/Graph Regression 9666 Epic: Migrate Knowledge Graph to Memory Core
subIssuesCompleted	12
subIssuesTotal	12
blockedBy	[]
blocking	[]
closedAt	Apr 4, 2026, 2:04 AM

Epic: Architecture - Neo.mjs Dream Mode & GraphRAG Swarm

Name: Neo.mjs Application Engine
Author: Neo.mjs

Closedepicaiarchitecture

tobiu commented on Apr 3, 2026, 12:42 PM

Problem / Context

The current Neo.mjs memory-core relies on flat vector embeddings (ChromaDB) for session summaries, which limits the agent's ability to reason about topological relationships, bug resolutions, and temporal connections.

To create a massive "performance multiplier", we need to introduce an asynchronous local LLM pipeline ("Dream Mode" powered by Gemma-4) that digests session episodic memories and constructs a definitive Knowledge Graph (the "Neocortex").

Proposed Solution (Hippocampus/Neocortex Architecture)

This epic coordinates the upgrade of the Neo.mjs AI infrastructure into a GraphRAG Swarm. The workloads are split contextually:

The Neocortex (knowledge-base server): Will host the unified SQLite Graph Database mapping both dynamic experiences and static AST relations.
The Hippocampus (memory-core server): Will host the "Night Shift" Dream Pipeline that leverages local Gemma-4 agents to extract lessons/patterns from episodic session memory and upsert them into the Neocortex graph.

Sub-Tasks

Epic 1: Local LLM Provider Adapter (Neo.ai.provider.Ollama targeted for gemma-4-31b-it).
Epic 2: Knowledge Graph Backend (GraphService.mjs inside knowledge-base).
Epic 3: The "Night Shift" REM Pipeline (DreamService.mjs inside memory-core).
Epic 4: Unified GraphRAG MCP Interface (New endpoints and query_knowledge_graph tool).
Epic 5: "Librarian" Sub-Agent Orchestration (Cross-agent task delegation in Agent.mjs).

tobiu added the epic label on Apr 3, 2026, 12:42 PM

tobiu added the ai label on Apr 3, 2026, 12:42 PM

tobiu added the architecture label on Apr 3, 2026, 12:42 PM

tobiu cross-referenced by #9639 on Apr 3, 2026, 12:44 PM

tobiu cross-referenced by #9642 on Apr 3, 2026, 12:44 PM

tobiu cross-referenced by #9643 on Apr 3, 2026, 12:44 PM

tobiu cross-referenced by #9641 on Apr 3, 2026, 12:44 PM

tobiu cross-referenced by #9640 on Apr 3, 2026, 12:44 PM

tobiu added sub-issue #9639 on Apr 3, 2026, 12:44 PM

tobiu added sub-issue #9640 on Apr 3, 2026, 12:44 PM

tobiu added sub-issue #9641 on Apr 3, 2026, 12:44 PM

tobiu added sub-issue #9642 on Apr 3, 2026, 12:44 PM

tobiu added sub-issue #9643 on Apr 3, 2026, 12:45 PM

tobiu assigned to @tobiu on Apr 3, 2026, 12:47 PM

tobiu added sub-issue #9658 on Apr 3, 2026, 3:48 PM

tobiu added sub-issue #9659 on Apr 3, 2026, 4:01 PM

tobiu cross-referenced by #9660 on Apr 3, 2026, 4:15 PM

tobiu added sub-issue #9660 on Apr 3, 2026, 4:15 PM

tobiu added sub-issue #9661 on Apr 3, 2026, 4:27 PM

tobiu cross-referenced by #9662 on Apr 3, 2026, 4:46 PM

tobiu added sub-issue #9662 on Apr 3, 2026, 4:46 PM

tobiu added sub-issue #9665 on Apr 3, 2026, 8:37 PM

tobiu added sub-issue #9666 on Apr 3, 2026, 11:44 PM

tobiu added parent issue #9671 on Apr 4, 2026, 1:49 AM

tobiu Apr 4, 2026, 2:04 AM

Superseded by the new Masterplan Epic #9671.

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