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	9666
title	Epic: Migrate Knowledge Graph to Memory Core
state	Closed
labels	epicai
assignees	tobiu
createdAt	Apr 3, 2026, 11:44 PM
updatedAt	Apr 4, 2026, 12:17 AM
githubUrl	https://github.com/neomjs/neo/issues/9666
author	tobiu
commentsCount	1
parentIssue	9638
subIssues	9667 Phase 1: Cleanse knowledge-base of Graph Logic 9668 Phase 2: Migrate Graph Service and OpenAPI to memory-core 9669 Phase 3: Unleash DreamService Graph Extraction
subIssuesCompleted	3
subIssuesTotal	3
blockedBy	[]
blocking	[]
closedAt	Apr 4, 2026, 12:17 AM

Epic: Migrate Knowledge Graph to Memory Core

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

Closedepicai

tobiu commented on Apr 3, 2026, 11:44 PM

Background

The knowledge-base server provides public framework insights (distributed in release ZIPs). The memory-core server handles private user history. DreamService translates private session histories into Graph Nodes. Keeping the Graph SQLite Database inside knowledge-base inherently risks exposing private memory nodes inside public graph zip bundles, and caused process locking when memory-core attempted cross-server imports.

The Graph database natively tracks episodic memories, so it must be owned exclusively by the memory-core MCP server.

Architecture Blueprint

Cleanse knowledge-base:
- Remove GraphService.mjs.
- Remove upsertNode from VectorService.mjs (L223-L231).
- Strip /graph/* routes from openapi.yaml.
Empower memory-core:
- Migrate GraphService.mjs natively into /memory-core/services/.
- Re-graft /graph/* routes into the memory-core/openapi.yaml mapping.
- Configure SQLite to target chroma-neo-memory-core/graph/knowledge-graph.sqlite.
Restore DreamService:
- Let DreamService.mjs import GraphService safely from its new local directory, avoiding all cross-process IPC locks.

tobiu added the epic label on Apr 3, 2026, 11:44 PM

tobiu added the ai label on Apr 3, 2026, 11:44 PM

tobiu added parent issue #9638 on Apr 3, 2026, 11:44 PM

tobiu cross-referenced by #9667 on Apr 3, 2026, 11:44 PM

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

tobiu cross-referenced by #9668 on Apr 3, 2026, 11:44 PM

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

tobiu cross-referenced by #9669 on Apr 3, 2026, 11:44 PM

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

tobiu assigned to @tobiu on Apr 3, 2026, 11:51 PM

tobiu Apr 4, 2026, 12:02 AM

We have fully migrated the Knowledge Graph from knowledge-base to memory-core resolving cross-process IPC locks and protecting episodic memory privacy.

tobiu closed this issue on Apr 4, 2026, 12:02 AM

tobiu reopened this issue on Apr 4, 2026, 12:04 AM

tobiu closed this issue on Apr 4, 2026, 12:17 AM