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	9814
title	Fix "undefined" Agent OS Graph Nodes in DreamService Gap Analysis
state	Closed
labels	bugai
assignees	tobiu
createdAt	Apr 9, 2026, 11:49 AM
updatedAt	Apr 9, 2026, 11:49 AM
githubUrl	https://github.com/neomjs/neo/issues/9814
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 9, 2026, 11:49 AM

Fix "undefined" Agent OS Graph Nodes in DreamService Gap Analysis

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

Closedbugai

tobiu commented on Apr 9, 2026, 11:49 AM

The Problem

The sandman_handoff.md file was generating undefined identifiers when logging Codebase Gaps via the REM Dream pipeline. This structural corruption disrupted the Native Edge Graph topological mapping and resulted from a property mapping mismatch during the TTL pruning cycle.

The Architectural Reality

The error originated in ai/mcp/server/memory-core/services/DreamService.mjs (around line 1005). The DreamService was iterating over GraphService.db.nodes.items and accessing node.name. Native nodes from SQLite map directly to an internal structure containing id, label, and properties. There is no root-level name property (it is stored mapping to properties.name).

File fixed:

ai/mcp/server/memory-core/services/DreamService.mjs

The Fix & Avoided Traps

Instead of globally refactoring the graph schema to hoist .name or applying a generic fallback logic (a "Gold Standard" LLM trap that can clutter Neo.mjs core), I targeted the most architecturally stable identifier: node.id string map (e.g., CLASS:Learning_Section_Markdown_Component). This natively protects the GraphRAG ingestion logs from ambiguity. The file has been modified to use \`${node.id}\`.

tobiu added the bug label on Apr 9, 2026, 11:49 AM

tobiu added the ai label on Apr 9, 2026, 11:49 AM

tobiu assigned to @tobiu on Apr 9, 2026, 11:49 AM

tobiu referenced in commit fbd2e7b - "fix(ai): Resolve undefined Graph Nodes in DreamService Gap Analysis (#9814)" on Apr 9, 2026, 11:49 AM

tobiu Apr 9, 2026, 11:49 AM

The native graph mapping issue in DreamService has been fixed by safely targeting the node.id representation mapped directly from the sqlite vector db, replacing the previous hallucination-prone node.name approach. Code is fully pushed!

tobiu closed this issue on Apr 9, 2026, 11:49 AM