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	9727
title	Semantic Refactoring of Memory Core Configuration
state	Closed
labels	enhancementairefactoringarchitecture
assignees	tobiu
createdAt	Apr 6, 2026, 1:13 AM
updatedAt	Apr 6, 2026, 1:57 AM
githubUrl	https://github.com/neomjs/neo/issues/9727
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 6, 2026, 1:48 AM

Semantic Refactoring of Memory Core Configuration

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

Closedenhancementairefactoringarchitecture

tobiu commented on Apr 6, 2026, 1:13 AM

Problem

The current memory core configuration (config.mjs) relies on misleading naming conventions: memoryDb and sessionDb are structurally defined as databases, when logically they are just collections/tables that live inside a physical database engine. Furthermore, ChromaManager uses eager initialization, meaning a simple file import triggers a background daemon run command—causing crash issues for unit tests where a server start is a fatal side behavior.

Proposed Solution

Semantic Separation: Decouple physical Engine routing from logical Collection schemas. We will introduce engines.neo and engines.chroma for directory and port routing, alongside a standalone collections block for table naming configurations.
Unified Backup Topology: Stick strictly to .jsonl data backups, creating a top-level backupPath across engines to prevent raw Chroma database folder copying/bloat.
Service Migration: Reconcile 8 existing framework files and build scripts to cleanly route to the semantic API paths.

tobiu added the enhancement label on Apr 6, 2026, 1:13 AM

tobiu added the ai label on Apr 6, 2026, 1:13 AM

tobiu added the refactoring label on Apr 6, 2026, 1:13 AM

tobiu added the architecture label on Apr 6, 2026, 1:13 AM

tobiu assigned to @tobiu on Apr 6, 2026, 1:13 AM

tobiu cross-referenced by #9728 on Apr 6, 2026, 1:23 AM

tobiu referenced in commit e12ee23 - "refactor: Semantic Refactoring of Memory Core Configuration (#9727)" on Apr 6, 2026, 1:47 AM

tobiu Apr 6, 2026, 1:48 AM

Architecture definition decoupled successfully and backwards compatibility for base sdk verified via SQLite Vector native.

tobiu closed this issue on Apr 6, 2026, 1:48 AM