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	7604
title	Epic: Automate MCP Server Startup and Reduce Agent Protocol
state	Closed
labels	enhancementepicai
assignees	tobiu
createdAt	Oct 22, 2025, 1:43 PM
updatedAt	Oct 26, 2025, 5:16 PM
githubUrl	https://github.com/neomjs/neo/issues/7604
author	tobiu
commentsCount	0
parentIssue	null
subIssues	7626 Cache Viewer Permission on Server Startup 7630 docs: Update AGENTS.md to Reflect MCP Server Architecture 7631 refactor: Remove obsolete buildScripts/ai directory 7658 Refactor: Simplify Memory Core Protocol in AGENTS.md 7659 Docs: Create Self-Explanatory Tools via OpenAPI Descriptions 7660 Refine Memory Protocol: Define a "Turn" and Consolidate Sub-Turns 7661 Refine Memory Protocol: Clarify Recovery and Prevent Skipped Turns 7662 Docs: Add Communication Style Directive to AGENTS.md
subIssuesCompleted	8
subIssuesTotal	8
blockedBy	[]
blocking	[]
closedAt	Oct 26, 2025, 5:16 PM

Epic: Automate MCP Server Startup and Reduce Agent Protocol

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

Closed v11.0.0 enhancementepicai

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

The current AGENTS.md file contains a significant number of manual steps that the AI agent must perform at the beginning of each session, such as checking if servers are running and triggering summarization. This process is brittle and places a high cognitive load on the agent.

This epic covers automating these startup procedures within the MCP servers themselves, with the primary goal of reducing the length and complexity of AGENTS.md by at least 70%.

Key Initiatives

Memory Core Automation:
- The memory-core server should automatically ensure its ChromaDB instance is running on startup.
- The server should automatically trigger the session summarization process on startup, removing the need for the agent to run npm run ai:summarize-session.
Knowledge Base Automation:
- The knowledge-base server should automatically ensure its ChromaDB instance is running on startup.
Protocol Simplification:
- Refactor AGENTS.md to remove all instructions related to manual server checks and startup procedures.
- The agent's initialization process should be simplified to just connecting to the running servers.

Benefits

Reduced Agent Complexity: Drastically simplifies the agent's bootstrap process.
Increased Reliability: Automating these steps makes the system more robust and less prone to user or agent error.
Faster Session Startup: Reduces the number of commands and checks required to start a new session.

tobiu added the enhancement label on Oct 22, 2025, 1:43 PM

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

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

tobiu added sub-issue #7626 on Oct 23, 2025, 5:06 PM

tobiu cross-referenced by #7626 on Oct 23, 2025, 5:06 PM

tobiu added sub-issue #7630 on Oct 24, 2025, 11:37 AM

tobiu added sub-issue #7631 on Oct 24, 2025, 12:15 PM

tobiu cross-referenced by #7634 on Oct 24, 2025, 12:43 PM

tobiu cross-referenced by #7658 on Oct 26, 2025, 10:53 AM

tobiu added sub-issue #7658 on Oct 26, 2025, 10:53 AM

tobiu cross-referenced by #7659 on Oct 26, 2025, 10:54 AM

tobiu added sub-issue #7659 on Oct 26, 2025, 10:54 AM

tobiu added sub-issue #7660 on Oct 26, 2025, 11:21 AM

tobiu added sub-issue #7661 on Oct 26, 2025, 11:34 AM

tobiu added sub-issue #7662 on Oct 26, 2025, 12:37 PM

tobiu cross-referenced by #7664 on Oct 26, 2025, 2:53 PM

tobiu closed this issue on Oct 26, 2025, 5:16 PM

tobiu assigned to @tobiu on Oct 26, 2025, 5:16 PM