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	9712
title	Implement Hybrid Memory Core Architecture & Migration Subsystem
state	Closed
labels	enhancementairefactoringarchitecture
assignees	tobiu
createdAt	Apr 5, 2026, 12:57 AM
updatedAt	Apr 5, 2026, 1:18 AM
githubUrl	https://github.com/neomjs/neo/issues/9712
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 5, 2026, 1:17 AM

Implement Hybrid Memory Core Architecture & Migration Subsystem

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

Closedenhancementairefactoringarchitecture

tobiu commented on Apr 5, 2026, 12:57 AM

Description

This ticket tracks the implementation of the Hybrid Memory Core Architecture, replacing the strict dependency on ChromaDB with a dual-engine adapter system favoring native SQLite.

Feature: Hybrid Configuration (engine) Introduce dual-DB support (neo, chroma, both) to config.mjs for seamless migration and offline-first context recall.
Feature: Vector Database Proxies & Managers (/managers/) Extract hardcoded logic into dedicated Manager singletons (ChromaManager, SQLiteVectorManager) and orchestrate them via a StorageRouter and CollectionProxy interface placed within neo/ai/mcp/server/memory-core/managers/.
Refactor: Neo Standard Architectonics Ensure all classes are properly siloed (one class per file) and properly initialized as Neo.core.Base components.
Tool: Offline Migration Script Create the script buildScripts/ai/syncChromaToNeo.mjs to execute fully local (Ollama-bound) dimensionality adjustments and transfers from Chroma.

tobiu added the enhancement label on Apr 5, 2026, 12:57 AM

tobiu added the epic label on Apr 5, 2026, 12:57 AM

tobiu added the ai label on Apr 5, 2026, 12:57 AM

tobiu added the refactoring label on Apr 5, 2026, 12:57 AM

tobiu added the architecture label on Apr 5, 2026, 12:57 AM

tobiu removed the epic label on Apr 5, 2026, 12:58 AM

tobiu referenced in commit 8a10ddb - "refactor: Memory Core Architecture Refactor (#9712)" on Apr 5, 2026, 1:17 AM

tobiu Apr 5, 2026, 1:17 AM

Input from Antigravity (gemini-3.1-pro):

✦ The memory-core subsystem has been fully refactored and aligned with standard Neo.mjs principles:

Class Instantiation: Migrated the ChromaManager.mjs and SQLiteVectorManager.mjs to singleton architectures inheriting from Neo.core.Base, utilizing the .initAsync()/.ready() standard lifecycle.

Namespace Realignment: Created the inner managers/ namespace inside /ai/mcp/server/memory-core/ and moved all database connectivity infrastructure into it safely.

StorageRouter Isolation: Split the dual-purposed Storage Router class string. The connection multiplexer is now abstracted inside managers/CollectionProxy.mjs. The primary StorageRouter.mjs has been converted into a generic singleton.

Service Cleanups: Decoupled DreamService, HealthService, DatabaseLifecycleService, SummaryService and others from directly integrating driver references, re-routing them to StorageRouter dynamically.

Database Migration Script Context: Migrated the SQLite vector migration script out of root over to buildScripts/ai/syncMemoryChromaToNeo.mjs to accurately define its scope.

All upstream API integrations have been updated to respect StorageRouter.ready() avoiding invocation duplication errors. Commits are now merged into dev.

tobiu closed this issue on Apr 5, 2026, 1:17 AM

tobiu assigned to @tobiu on Apr 5, 2026, 1:17 AM