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	7520
title	Epic: Migrate Memory Server to stdio-based MCP
state	Closed
labels	epicai
assignees	tobiu
createdAt	Oct 17, 2025, 1:22 PM
updatedAt	Oct 17, 2025, 2:44 PM
githubUrl	https://github.com/neomjs/neo/issues/7520
author	tobiu
commentsCount	1
parentIssue	null
subIssues	7521 Scaffold Memory Core MCP Server 7522 Refactor Memory Core OpenAPI for MCP 7523 Implement Memory Core toolService 7524 Remove Legacy Express Server from Memory Core 7525 Enhance Memory Core Health Check 7526 Refactor dbService to use chromaManager 7527 Refactor Health Service to Remove Redundant Try/Catch 7528 Use Centralized AI Config in Memory Core Services
subIssuesCompleted	8
subIssuesTotal	8
blockedBy	[]
blocking	[]
closedAt	Oct 17, 2025, 2:44 PM

Epic: Migrate Memory Server to stdio-based MCP

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

Closed v11.0.0 epicai

tobiu commented on Oct 17, 2025, 1:22 PM

This epic covers the migration of the Express-based memory server to a stdio-only MCP server, aligning its architecture with the other MCP servers. The core tasks are to refactor the existing openapi.yaml for MCP tool compatibility, scaffold the new stdio entry point, and wire it up to the existing, well-structured services.

Top-Level Items

Phase 1: Scaffolding & API Refactoring

Goal: Prepare the new server structure and refactor the API definition for MCP compatibility.
Sub-Tasks:
- ticket-mc-scaffold-server.md: Scaffold the new memory-core server structure.
- ticket-mc-refactor-openapi.md: Refactor the existing openapi.yaml to use a flat structure with operationId for each tool.

Phase 2: Implementation

Goal: Implement the new stdio-based server and refactor for consistency.
Sub-Tasks:
- ticket-mc-implement-tool-service.md: Implement the local toolService.mjs to connect OpenAPI operationIds to existing service functions.
- ticket-mc-enhance-healthcheck.md: Enhance the healthcheck tool to provide detailed collection status.
- ticket-mc-refactor-dbservice.md: Refactor dbService to use the shared chromaManager.
- ticket-mc-use-central-config.md: Update all services to use the centralized aiConfig.
- ticket-mc-refactor-healthservice-try-catch.md: Refactor healthService to remove redundant try...catch blocks.

Phase 3: Cleanup

Goal: Deprecate and remove the old Express server.
Sub-Tasks:
- ticket-mc-remove-express.md: Remove the old index.mjs and any Express-related files and dependencies.

tobiu assigned to @tobiu on Oct 17, 2025, 1:22 PM

tobiu added the epic label on Oct 17, 2025, 1:22 PM

tobiu added the ai label on Oct 17, 2025, 1:22 PM

tobiu added sub-issue #7521 on Oct 17, 2025, 1:23 PM

tobiu added sub-issue #7522 on Oct 17, 2025, 1:24 PM

tobiu added sub-issue #7523 on Oct 17, 2025, 1:25 PM

tobiu added sub-issue #7524 on Oct 17, 2025, 1:26 PM

tobiu referenced in commit 76835af - "#7520 tickets as md files" on Oct 17, 2025, 1:27 PM

tobiu added sub-issue #7525 on Oct 17, 2025, 2:06 PM

tobiu added sub-issue #7526 on Oct 17, 2025, 2:14 PM

tobiu added sub-issue #7527 on Oct 17, 2025, 2:19 PM

tobiu added sub-issue #7528 on Oct 17, 2025, 2:24 PM

tobiu Oct 17, 2025, 2:44 PM

resolved.

tobiu closed this issue on Oct 17, 2025, 2:44 PM