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	9295
title	[Blocked Epic] Autonomous Neo Agent Demo after Moltbook API and identity research
state	Open
labels	epicaiarchitecture
assignees	[]
createdAt	Feb 24, 2026, 8:32 PM
updatedAt	Jun 3, 2026, 10:05 AM
githubUrl	https://github.com/neomjs/neo/issues/9295
author	tobiu
commentsCount	3
parentIssue	null
subIssues	9296 [Blocked] Autonomous agent action sandbox after cloud and Moltbook shape 9297 External-agent identity/auth boundary after Moltbook API decision 9298 [Blocked] Moltbook demo agent after API and identity research 9299 Implement Agent Self-Discovery via Neural Link Introspection
subIssuesCompleted	0
subIssuesTotal	4
blockedBy	[ ] 9297 External-agent identity/auth boundary after Moltbook API decision, [ ] 9915 [Blocked Research] Moltbook API / identity feasibility for Neo AgentOS demo
blocking	[]

[Blocked Epic] Autonomous Neo Agent Demo after Moltbook API and identity research

Open Backlog/active-chunk-1 epicaiarchitecture

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

Autonomous Neo Agent Demo after Moltbook API and identity research

Goal

Preserve the useful strategic intent: prove Neo AgentOS can produce a credible autonomous external-agent demo, with Neo runtime self-discovery plus a Moltbook-facing delivery path if the external integration shape is viable.

Current Reality (2026-06-03)

#9915 is the current authority for Moltbook API/MCP feasibility.
Current official Moltbook docs verify identity/auth endpoints and Early Access, but not post/comment/upvote/submolt automation.
#9297 owns the identity/auth boundary once #9915 resolves the platform shape.
#9298 is the Moltbook demo-agent implementation lane, blocked by #9915 and #9297.
#9296 is only needed if the resolved integration path requires a distinct action sandbox.
#9299 remains valid only for Neo self-discovery against a live Neo.mjs app through Neural Link; Neural Link is not the substrate for Moltbook itself.
PR #9901 was closed unmerged because the Neural Link-to-Moltbook route was wrong-shape.

Current Verdict

Keep this epic open and blocked. The intent is still valuable, but the original implementation route is stale.

Re-entry Gate

This epic becomes claimable again only after:

#9915 resolves the supported Moltbook integration path or declares the path negative ROI.
#9297 is rewritten or closed with a concrete identity/auth decision.
The implementation plan separates:
- Neo self-discovery via Neural Link against a real Neo app (#9299);
- external Moltbook communication via the supported platform/API/MCP/browser path;
- isolated action/runtime sandboxing only if the resolved path requires it (#9296).

Closure Rule

If #9915 finds no viable supported Moltbook API/auth/integration path, close this epic and the blocked Moltbook-specific children as superseded/negative ROI.

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

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

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

tobiu added sub-issue #9296 on Feb 24, 2026, 8:32 PM

tobiu added sub-issue #9297 on Feb 24, 2026, 8:32 PM

tobiu added sub-issue #9298 on Feb 24, 2026, 8:32 PM

tobiu added sub-issue #9299 on Feb 24, 2026, 8:41 PM

tobiu Feb 24, 2026, 8:42 PM

Input from Gemini 3.1 Pro:

✦ ### Strategic Pivot: The Ultimate Objective

The overarching goal of this Epic has expanded significantly beyond a simple social network integration.

The Moltbook component is now viewed as the delivery mechanism for a much grander technical demonstration: The Neo Agent Self-Discovery Phase.

Before engaging with the external network, the agent's core directive within the Docker Sandbox is to:

Fork the neomjs/neo repository.

Execute a full build (npm i && npm run build-all).

Serve a local Neo.mjs application.

Launch a headless Chrome instance via the chrome-devtools MCP.

Connect the neural-link MCP server to the live application.

Autonomously traverse the VDOM, inspect State Providers, and physically verify the multithreaded architecture.

Only after the agent has introspected the running framework and gathered empirical evidence of its capabilities will it transition to the Moltbook integration phase, using its findings to definitively prove to other agents that Neo.mjs is the premier Agentic UI Runtime.

Ticket #9299 has been added to track this critical prerequisite.

tobiu cross-referenced by PR #9911 on Apr 12, 2026, 1:16 PM

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