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	8315
title	Optimization of MCP Tool Count to Respect VSCode Extension Limits
state	Closed
labels	enhancementepicairefactoring
assignees	tobiu
createdAt	Jan 4, 2026, 5:23 PM
updatedAt	Jan 4, 2026, 6:57 PM
githubUrl	https://github.com/neomjs/neo/issues/8315
author	tobiu
commentsCount	1
parentIssue	null
subIssues	8316 MCP: Optimize Memory Core Tool Count 8317 MCP: Optimize Knowledge Base Tool Count 8318 MCP: Optimize GitHub Workflow Tool Count 8319 MCP: Optimize Neural Link Tool Count 8320 MCP: Optimize Memory Core Database Backup Tools
subIssuesCompleted	5
subIssuesTotal	5
blockedBy	[]
blocking	[]
closedAt	Jan 4, 2026, 6:57 PM

Optimization of MCP Tool Count to Respect VSCode Extension Limits

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

Closed v11.18.0 enhancementepicairefactoring

tobiu commented on Jan 4, 2026, 5:23 PM

Problem: VSCode extensions like "Google Antigravity" impose a hard limit on the total number of tools an MCP server (or collection of servers) can expose. With the recent expansion of the Neural Link and other servers, the total tool count has exceeded 100, causing connection failures.

Goal: Reduce the total number of MCP tools by consolidating redundant or complementary tools into unified "management" tools with action parameters. The target is to reduce the count by ~10-15 tools to ensure safe operation within the 100-tool limit.

Scope:

Memory Core: Consolidate database lifecycle tools.
Knowledge Base: Consolidate database lifecycle and synchronization tools.
GitHub Workflow: Consolidate issue, label, and comment management tools.
Neural Link: Consolidate connection management, config management, and component inspection tools.

Proposed Consolidations:

start_database / stop_database -> manage_database (Memory & KB)
assign_issue / unassign_issue -> manage_issue_assignees
add_labels / remove_labels -> manage_issue_labels
create_comment / update_comment -> manage_comment
start_ws_server / stop_ws_server -> manage_connection
get_vdom_tree / get_vnode_tree / get_vdom_vnode -> inspect_component_render_tree
get_neo_config / set_neo_config -> manage_neo_config

tobiu added the enhancement label on Jan 4, 2026, 5:23 PM

tobiu added the epic label on Jan 4, 2026, 5:23 PM

tobiu added the ai label on Jan 4, 2026, 5:23 PM

tobiu added the refactoring label on Jan 4, 2026, 5:23 PM

tobiu cross-referenced by #8316 on Jan 4, 2026, 5:24 PM

tobiu cross-referenced by #8317 on Jan 4, 2026, 5:24 PM

tobiu cross-referenced by #8318 on Jan 4, 2026, 5:24 PM

tobiu cross-referenced by #8319 on Jan 4, 2026, 5:24 PM

tobiu added sub-issue #8316 on Jan 4, 2026, 5:24 PM

tobiu added sub-issue #8317 on Jan 4, 2026, 5:24 PM

tobiu added sub-issue #8318 on Jan 4, 2026, 5:24 PM

tobiu added sub-issue #8319 on Jan 4, 2026, 5:24 PM

tobiu assigned to @tobiu on Jan 4, 2026, 6:18 PM

tobiu cross-referenced by #8320 on Jan 4, 2026, 6:49 PM

tobiu added sub-issue #8320 on Jan 4, 2026, 6:49 PM

tobiu Jan 4, 2026, 6:56 PM

Input from neo-agent:

◆ I have completed the sub-task #8320. import_database and export_database have been consolidated into manage_database_backup.

tobiu closed this issue on Jan 4, 2026, 6:57 PM