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	9774
title	Refactor AI SDK and Build Scripts for Memory Core Module Decoupling
state	Closed
labels	enhancementaibuild
assignees	tobiu
createdAt	Apr 8, 2026, 12:40 AM
updatedAt	Apr 8, 2026, 12:42 AM
githubUrl	https://github.com/neomjs/neo/issues/9774
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 8, 2026, 12:42 AM

Refactor AI SDK and Build Scripts for Memory Core Module Decoupling

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

Closedenhancementaibuild

tobiu commented on Apr 8, 2026, 12:40 AM

Problem

The legacy DatabaseLifecycleService inside the Memory Core was recently decoupled into ChromaLifecycleService and InferenceLifecycleService. Several downstream consumers across buildScripts/ai/ and ai/examples/ were left statically referencing the deleted service, breaking core SDK functions.

Solution

Introduce a facade SystemLifecycleService inside memory-core/services/lifecycle that orchestrates both internal services.
Export this orchestrator via ai/services.mjs as Memory_LifecycleService to preserve compatibility.
Update hardcoded static imports across all build scripts and examples.

tobiu added the enhancement label on Apr 8, 2026, 12:40 AM

tobiu added the ai label on Apr 8, 2026, 12:40 AM

tobiu added the build label on Apr 8, 2026, 12:40 AM

tobiu assigned to @tobiu on Apr 8, 2026, 12:40 AM

tobiu referenced in commit 22c5db8 - "refactor: Orchestrate Memory Core startup via SystemLifecycleService facade (#9774)" on Apr 8, 2026, 12:42 AM

tobiu Apr 8, 2026, 12:42 AM

Refactored the Memory Core AI SDK downstream references by establishing a SystemLifecycleService facade, protecting downstream consumers. Modified integration code locally and verified startup dependencies across build scripts and examples.

tobiu closed this issue on Apr 8, 2026, 12:42 AM

tobiu referenced in commit 0e32592 - "test(mcp): resolve concurrent _initPromise yield bypass race during parallel worker Playwright execution (#9774)" on Apr 8, 2026, 1:27 AM

tobiu referenced in commit 15e3c95 - "chore(mcp): align ChromaLifecycleService JSDocs and extract registerCleanup (#9774)" on Apr 8, 2026, 1:27 AM