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	7389
title	Investigate Worker Console Access with MCP
state	Closed
labels	enhancementstaleai
assignees	tobiu
createdAt	Oct 6, 2025, 12:36 PM
updatedAt	Jan 9, 2026, 1:57 AM
githubUrl	https://github.com/neomjs/neo/issues/7389
author	tobiu
commentsCount	4
parentIssue	7385
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 9, 2026, 1:57 AM

Investigate Worker Console Access with MCP

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

Closed v11.19.0 enhancementstaleai

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

This ticket is for investigating the feasibility of accessing worker and shared worker consoles using the Chrome DevTools Model Context Protocol (MCP) server. This is a crucial step in enabling full-stack debugging in our multi-threaded application.

Acceptance Criteria

A research document is created that summarizes the findings.
The document answers the following questions: a. Can we access the console logs of app workers? b. Can we access the console logs of shared workers? c. What are the limitations, if any?
The document provides code examples or links to relevant documentation to support the findings.

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

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

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

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

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

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

tobiu assigned to @tobiu on Oct 6, 2025, 5:37 PM

tobiu removed the help wanted label on Oct 6, 2025, 5:37 PM

tobiu removed the good first issue label on Oct 6, 2025, 5:37 PM

tobiu removed the hacktoberfest label on Oct 6, 2025, 5:37 PM

tobiu Oct 6, 2025, 5:38 PM

I tested this one, and sadly neither access to dedicated nor shared workers is possible yet. Remote method access comes to the rescue.

tobiu Oct 8, 2025, 4:00 PM

I added 2 new feature requests for dedicated & shared workers support inside the mcp-server repo. Adding the links here for cross reference, and enable others to see the status.

Dedicated Workers: https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/316

Shared Workers: https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/317

@github-actions - 2026-01-07T03:10:01Z

This issue is stale because it has been open for 90 days with no activity.

2026-01-07T03:10:01Z @github-actions added the stale label

tobiu Jan 9, 2026, 1:57 AM

Input from Gemini 3 Pro:

✦ Status Update: Obsolete

This investigation is no longer relevant. The Neural Link (v11.18.0+) provides native access to the Neo.mjs runtime environment, including state and component hierarchies across workers, rendering raw console access via DevTools unnecessary for agentic workflows.

Action: Closing as superseded by the Neural Link architecture.

tobiu closed this issue on Jan 9, 2026, 1:57 AM