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	9298
title	Implement Moltbook Demo Agent using Chrome DevTools MCP
state	Open
labels	enhancementai
assignees	[]
createdAt	Feb 24, 2026, 8:32 PM
updatedAt	Feb 24, 2026, 8:38 PM
githubUrl	https://github.com/neomjs/neo/issues/9298
author	tobiu
commentsCount	1
parentIssue	9295
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]

Implement Moltbook Demo Agent using Chrome DevTools MCP

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

Openenhancementai

tobiu commented on Feb 24, 2026, 8:32 PM

Problem

We need an end-to-end integration test of the Neo AI infrastructure (Orchestrator + Memory Core + Knowledge Base + Sandbox) proving it can operate autonomously on the web.

Solution

Build ai/demo-agents/moltbook/Agent.mjs.

Extend Neo.ai.Agent.
Connect to the chrome-devtools MCP server for web navigation and interaction.
Utilize the ai/services.mjs SDK to bypass MCP serialization for fast, direct access to ChromaDB (Memory/Knowledge).
Utilize the new Programmatic Identity to autonomously sign up for moltbook.com, read posts, and reply with technical context sourced from the Neo.mjs knowledge base.

tobiu added the enhancement label on Feb 24, 2026, 8:32 PM

tobiu added the ai label on Feb 24, 2026, 8:32 PM

tobiu added parent issue #9295 on Feb 24, 2026, 8:32 PM

tobiu Feb 24, 2026, 8:38 PM

Input from Gemini 3.1 Pro:

✦ ### Architectural Context: Connecting to Chrome DevTools

For the implementation of this agent, we do not need to build a custom Playwright bridge or a native Neo MCP server for browser automation.

Because the Neo.ai.mcp.client.Client acts as a generic wrapper around the official @modelcontextprotocol/sdk, it can spawn external MCP servers via npx just as easily as it spawns our local Node.js scripts.

To grant the Orchestrator's Loop full control over a headless browser (including the 28 native tools for navigation, clicking, form filling, and DOM evaluation), we simply need to append the official chrome-devtools-mcp server to the client configuration (e.g., in ai/mcp/client/config.mjs or a dedicated config file for the Moltbook agent):
{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-puppeteer",
        "chrome-devtools-mcp@latest",
        "--channel=canary",
        "--headless=true",
        "--isolated=true"
      ]
    }
  }
}
(Note: Ensure the exact package name/args match the current official MCP Puppeteer/DevTools release at the time of implementation).

This provides the agent with the necessary "hands and eyes" to interact with the external Moltbook platform while preserving the neural-link MCP server for our internal, deep-introspection pairing tasks.