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	7385
title	''Sighted'' Agent - Chrome DevTools Integration
state	Closed
labels	help wantedgood first issueepicstalehacktoberfestai
assignees	tobiu
createdAt	Oct 6, 2025, 11:03 AM
updatedAt	Jan 9, 2026, 1:57 AM
githubUrl	https://github.com/neomjs/neo/issues/7385
author	tobiu
commentsCount	2
parentIssue	null
subIssues	7386 Configure MCP Server for Project 7387 Create Guide for Chrome DevTools MCP Server 7388 Define the "Sighted" Development Workflow 7389 Investigate Worker Console Access with MCP 7390 Create a "Sighted" Development Demo
subIssuesCompleted	5
subIssuesTotal	5
blockedBy	[]
blocking	[]
closedAt	Jan 9, 2026, 1:57 AM

'Sighted' Agent - Chrome DevTools Integration

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

Closed v11.19.0 help wantedgood first issueepicstalehacktoberfestai

tobiu commented on Oct 6, 2025, 11:03 AM

This epic covers the integration of the Chrome DevTools Model Context Protocol (MCP) server into the neo.mjs development workflow. The primary goal is to give the AI agent 'sight' by allowing it to programmatically interact with a live browser instance. This will enable a new, interactive development workflow where the agent can:

Continuously verify UI changes: Inspect the DOM and CSS in real-time during component development.
Generate meaningful Playwright tests: Leverage its understanding of the UI to create robust Playwright tests.
Debug multi-threaded applications: Investigate worker and shared worker console access for comprehensive debugging.
Analyze performance and automate user flows: Utilize advanced DevTools capabilities for performance analysis and UI automation.

This initiative is a critical step towards building a more powerful and autonomous AI-native development environment, transforming the agent from a 'blind' code generator into a 'sighted' development partner.

Top-Level Items & Implementation Phases

Phase 1: Initial Integration & Verification

Goal: Configure the MCP server and verify basic connectivity and functionality.

Phase 2: 'Sighted' Development Workflow

Goal: Integrate browser-based verification into the agent's core development and PR review workflows.

Sub-Tasks

Phase 1: Initial Integration & Verification

Done: ticket-configure-mcp-server.md
To Do: ticket-create-mcp-server-guide.md

Phase 2: 'Sighted' Development Workflow

To Do: ticket-define-sighted-development-workflow.md
To Do: ticket-investigate-worker-console-access-with-mcp.md
To Do: ticket-create-sighted-development-demo.md

tobiu assigned to @tobiu on Oct 6, 2025, 11:03 AM

tobiu added the epic label on Oct 6, 2025, 11:03 AM

tobiu added the ai label on Oct 6, 2025, 11:03 AM

tobiu added sub-issue #7386 on Oct 6, 2025, 11:04 AM

tobiu added sub-issue #7387 on Oct 6, 2025, 12:29 PM

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

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

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

tobiu added sub-issue #7388 on Oct 6, 2025, 12:34 PM

tobiu added sub-issue #7389 on Oct 6, 2025, 12:36 PM

tobiu added sub-issue #7390 on Oct 6, 2025, 12:38 PM

tobiu referenced in commit d071c95 - "#7385 ticket md files" on Oct 6, 2025, 12:41 PM

tobiu Jan 9, 2026, 1:57 AM

Input from Gemini 3 Pro:

✦ Status Update: Obsolete

This initiative has been superseded by the Neural Link architecture introduced in v11.18.0 and matured in v11.19.0.

Rationale: The original goal was to give agents "sight" via the generic Chrome DevTools protocol. However, we found that a native, engine-aware introspection layer (Neural Link) provides vastly superior capabilities:

Scene Graph Awareness: The Neural Link understands Neo.component.Base instances, not just DOM nodes.

State Mutation: Agents can modify runtime state directly, which DevTools cannot do safely.

Cross-Context: The Neural Link bridges the Worker boundary natively.

As of v11.19.0, we have officially removed the Chrome DevTools MCP server from our default configuration in favor of the Neural Link.

Action: Closing as superseded.

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