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	7871
title	Refactor Knowledge Base MCP Server to use Neo.core.Base architecture
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Nov 23, 2025, 11:33 AM
updatedAt	Nov 23, 2025, 11:38 AM
githubUrl	https://github.com/neomjs/neo/issues/7871
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Nov 23, 2025, 11:38 AM

Refactor Knowledge Base MCP Server to use Neo.core.Base architecture

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

Closed v11.9.0 enhancementai

tobiu commented on Nov 23, 2025, 11:33 AM

Objective: Refactor the Knowledge Base MCP server entry point to align with the Neo.mjs architecture by encapsulating the server logic within a Neo.core.Base class. This applies the same proven pattern used for the Memory Core server.

Changes:

Create ai/mcp/server/knowledge-base/Server.mjs:
- Define class Server extends Neo.core.Base.
- Class Fields: configFile, mcpServer, transport.
- initAsync():
  - Call super.initAsync().
  - Load custom config via aiConfig.load() if this.configFile is set.
  - Initialize McpServer instance.
  - Set up request handlers (listTools, callTool).
  - Await DatabaseService.ready().
  - Perform HealthService.healthcheck() and log status.
  - Initialize and connect StdioServerTransport.
- Methods: Extract helper methods for setupRequestHandlers and logStartupStatus.
Refactor ai/mcp/server/knowledge-base/mcp-stdio.mjs:
- Convert into a lightweight "runner" script.
- Imports: Ensure correct order: Neo -> core/_export -> InstanceManager -> aiConfig -> logger -> Server.
- Logic:
  - Parse CLI arguments (-d, -c).
  - Update aiConfig.data.debug immediately.
  - Instantiate Server inside a try/catch block.
  - Use top-level await to wait for server.ready().
  - Handle errors cleanly (log and exit).

Technical Details:

Replicates the robust architecture from the Memory Core refactoring.
Ensures consistent lifecycle management and error handling.

tobiu assigned to @tobiu on Nov 23, 2025, 11:33 AM

tobiu added the enhancement label on Nov 23, 2025, 11:33 AM

tobiu added the ai label on Nov 23, 2025, 11:33 AM

tobiu referenced in commit 6e346a9 - "Refactor Knowledge Base MCP Server to use Neo.core.Base architecture #7871" on Nov 23, 2025, 11:38 AM

tobiu closed this issue on Nov 23, 2025, 11:38 AM

tobiu Nov 23, 2025, 11:38 AM

Input from Gemini:

✦ The Knowledge Base MCP server has been successfully refactored to use the Neo.core.Base architecture.

Implementation Highlights:

Server.mjs: New class that manages the server lifecycle (initAsync), service dependencies (DatabaseService), and MCP transport. It uses class fields for configFile, mcpServer, and transport.

mcp-stdio.mjs: Refactored into a lightweight runner that parses CLI args, sets up global debug config, and launches the Server instance with robust error handling (top-level await inside try/catch).

Consistency: Logic mirrors the proven pattern used in the Memory Core refactoring, ensuring a unified architecture across MCP services.