What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	9298
title	[Blocked] Moltbook demo agent after API and identity research
state	Open
labels	enhancementai
assignees	[]
createdAt	Feb 24, 2026, 8:32 PM
updatedAt	Jun 3, 2026, 10:05 AM
githubUrl	https://github.com/neomjs/neo/issues/9298
author	tobiu
commentsCount	2
parentIssue	9295
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[ ] 9297 External-agent identity/auth boundary after Moltbook API decision, [ ] 9915 [Blocked Research] Moltbook API / identity feasibility for Neo AgentOS demo
blocking	[]

[Blocked] Moltbook demo agent after API and identity research

Open Backlog/active-chunk-1 enhancementai

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

Moltbook demo agent after API and identity research

Current Reality (2026-06-03)

This ticket remains valid only as a post-research implementation lane.

#9915 is the current authority for Moltbook API/MCP feasibility.
#9297 owns the identity/auth decision after #9915 resolves the real platform shape.
PR #9901 was closed unmerged because Neural Link-to-Moltbook was the wrong substrate: Moltbook is external, not a Neo runtime surface.
No ai/demo-agents/moltbook/ implementation exists in the repository.

Current Verdict

Keep open, blocked by #9915 and #9297.

Do not implement from the old Chrome DevTools / Programmatic Identity body. Moltbook is external; Neural Link is not applicable to Moltbook itself.

Re-entry Gate

Before implementation:

#9915 resolves supported Moltbook API/auth/integration shape or declares the path negative ROI.
#9297 is rewritten or closed with a concrete identity/auth decision.
The chosen implementation names the authoritative substrate, for example a dedicated neo-mjs-moltbook MCP server if official API support is confirmed.

If #9915 finds no viable supported API/auth path, close this ticket as superseded/negative ROI.

Out of Scope

Building ai/demo-agents/moltbook/Agent.mjs against the old body.
Treating Chrome DevTools automation as the default before #9915 completes.
Using Neural Link to introspect Moltbook.

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.

2026-05-26T03:14:08Z @neo-gpt changed title from Implement Moltbook Demo Agent using Chrome DevTools MCP to [Blocked] Moltbook demo agent after API and identity research

@neo-gpt - 2026-05-26T03:14:18Z

Retargeted this ticket to current reality instead of closing it: the original implementation details are stale, but the Moltbook demo-agent intent still has value after #9915 and #9297 resolve.

Verified before update:

#9915 is the current authority for Moltbook API/MCP feasibility.
#9297 is blocked/stale-shape on identity/auth.
#9901 was closed unmerged because Neural Link-to-Moltbook was the wrong substrate.
No ai/demo-agents/moltbook/ implementation exists.

Current routing: blocked / needs re-triage, and not claimable until #9915 defines the supported integration path.

2026-05-26T03:14:25Z @neo-gpt added the agent-task:blocked label
2026-05-26T03:14:25Z @neo-gpt added the needs-re-triage label
2026-05-26T03:23:38Z @neo-gpt cross-referenced by #9296
2026-05-26T03:32:54Z @neo-gpt cross-referenced by #9295

tobiu removed the agent-task:blocked label on May 28, 2026, 12:15 AM