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	7387
title	Create Guide for Chrome DevTools MCP Server
state	Closed
labels	documentationenhancementhelp wantedgood first issuehacktoberfestai
assignees	kart-u
createdAt	Oct 6, 2025, 12:29 PM
updatedAt	Oct 8, 2025, 10:57 PM
githubUrl	https://github.com/neomjs/neo/issues/7387
author	tobiu
commentsCount	2
parentIssue	7385
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Oct 8, 2025, 10:57 PM

Create Guide for Chrome DevTools MCP Server

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

Closed v11.0.0 documentationenhancementhelp wantedgood first issuehacktoberfestai

tobiu commented on Oct 6, 2025, 12:29 PM

To ensure that human and AI developers can successfully set up and use the Chrome DevTools Model Context Protocol (MCP) server, a new guide needs to be created. This guide will live in learn/guides/ai/ and will provide clear instructions for installation and troubleshooting.

Acceptance Criteria

A new markdown file is created at learn/guides/ai/ChromeDevToolsMcpServer.md.
The guide explains the purpose of the MCP server.
The guide explicitly states that Node.js v22.12.0 or higher is a strict requirement.
The guide explains how the MCP server is configured in .gemini/settings.json.
The guide provides basic troubleshooting steps, including how to check the server status and log files.

tobiu added the documentation label on Oct 6, 2025, 12:29 PM

tobiu added the enhancement label on Oct 6, 2025, 12:29 PM

tobiu added parent issue #7385 on Oct 6, 2025, 12:29 PM

tobiu added the help wanted label on Oct 6, 2025, 12:29 PM

tobiu added the good first issue label on Oct 6, 2025, 12:29 PM

tobiu added the hacktoberfest label on Oct 6, 2025, 12:29 PM

tobiu added the ai label on Oct 6, 2025, 12:29 PM

tobiu referenced in commit 522e5d0 - "#7387 early draft version" on Oct 6, 2025, 12:32 PM

tobiu Oct 6, 2025, 10:40 PM

This is a really exciting epic from a R&D perspective (literally bleeding edge).

Hint: for the MCP server to run, you need node v22.20 or higher. Otherwise gemini fails silently when trying to start it (damn, this did cost me time).

Let me give you more input:

Gemini tried several commands at first, none worked. Then it googled for quite some time. Result: "After installation, using this server requires restarting the terminal, meaning ending our session. Why did Google not include such a crucial detail into their blog post?"

The memory core resolved this gracefully (not starting from 0 again):

Current testing:

DOM access works, and this is indeed huge, since Gemini can now examine the output of code. After the MCP server is started, Gemini was self-aware of the available tools. However, I think this guide is still valuable, even when it means maintenance work for us when the server gets extended.

tobiu assigned to @kart-u on Oct 6, 2025, 10:40 PM

tobiu closed this issue on Oct 8, 2025, 10:57 PM

tobiu referenced in commit 9ca5314 - "Create Guide for Chrome DevTools MCP Server #7387" on Oct 8, 2025, 10:57 PM

tobiu referenced in commit dc6ee30 - "#7387 md ticket update (issue number was missing)" on Oct 8, 2025, 11:01 PM