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	9831
title	fix: Explicitly import Observable mixin to prevent static evaluation crashes in MCP servers
state	Closed
labels	bugai
assignees	tobiu
createdAt	Apr 9, 2026, 8:15 PM
updatedAt	Apr 9, 2026, 8:16 PM
githubUrl	https://github.com/neomjs/neo/issues/9831
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 9, 2026, 8:16 PM

fix: Explicitly import Observable mixin to prevent static evaluation crashes in MCP servers

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

Closedbugai

tobiu commented on Apr 9, 2026, 8:15 PM

The Problem

The memory-core and knowledge-base MCP daemon servers crash silently at boot time. This triggers context deadline exceeded connection timeouts in external clients like Gemini or Cline. The root cause is an Error: Attempting to mixin an undefined class: Neo.core.Observable thrown during static file evaluation.

The Architectural Reality

In ChromaLifecycleService.mjs and DatabaseLifecycleService.mjs, the class config declares static observable = true;. However, neither file explicitly imports the Neo.core.Observable module. When SystemLifecycleService.mjs statically imports ChromaLifecycleService, it forces Node to execute Neo.setupClass() synchronously before initAsync or environment configuration (such as bypassing Chroma in favor of aiConfig.engine = 'neo') can occur. Because module import order and timing can occasionally mask this in other files where Observable happens to be statically cached sooner, it results in intermittent but highly fatal swarm drop-outs depending on the engine's lazy loader.

Avoided Traps & Gold Standards

Trap Avoided: Wasting time debugging $PATH issues, missing chroma binaries, or .venv configurations. The crash happens during static evaluation before any spawn('chroma') commands can execute.
Trap Avoided: Assuming the framework was ignoring the default neo SQLite configuration. The config is correct, but it acts as a runtime gate that is blocked by the static evaluation crash.
Solution: We will add the explicit Observable imports at the top of both lifecycle services to ensure the mixin is defined reliably during Neo.setupClass().

Path Forward

Inject import Observable from '../../../../../../src/core/Observable.mjs'; into:

ai/mcp/server/memory-core/services/lifecycle/ChromaLifecycleService.mjs
ai/mcp/server/knowledge-base/services/DatabaseLifecycleService.mjs

tobiu added the bug label on Apr 9, 2026, 8:15 PM

tobiu added the ai label on Apr 9, 2026, 8:15 PM

tobiu assigned to @tobiu on Apr 9, 2026, 8:16 PM

tobiu referenced in commit fd59c1e - "fix: Explicitly import Observable mixin in MCP lifecycle services (#9831)" on Apr 9, 2026, 8:16 PM

tobiu Apr 9, 2026, 8:16 PM

Input from Antigravity (Gemini):

✦ The explicit Observable.mjs imports have been added to both ChromaLifecycleService.mjs and DatabaseLifecycleService.mjs. Tested locally using node ai/mcp/server/memory-core/mcp-server.mjs. The unhandled static evaluation crash is completely resolved, and the node daemon now transitions successfully to the MCP stdio transport handshake without triggering any context deadline exceeded timeouts.

tobiu closed this issue on Apr 9, 2026, 8:16 PM