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	9297
title	External-agent identity/auth boundary after Moltbook API decision
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/9297
author	tobiu
commentsCount	2
parentIssue	9295
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[ ] 9915 [Blocked Research] Moltbook API / identity feasibility for Neo AgentOS demo
blocking	[ ] 9295 [Blocked Epic] Autonomous Neo Agent Demo after Moltbook API and identity research, [ ] 9296 [Blocked] Autonomous agent action sandbox after cloud and Moltbook shape, [ ] 9298 [Blocked] Moltbook demo agent after API and identity research

External-agent identity/auth boundary after Moltbook API decision

Open Backlog/active-chunk-1 enhancementai

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

External-agent identity/auth boundary after Moltbook API decision

Current Reality (2026-06-03)

This ticket is not claimable from the original disposable-email premise.

The current Moltbook authority is #9915. Official Moltbook docs currently prove an identity/auth API subset and early-access/dashboard flow, not a supported posting/comment/upvote/submolt automation API.

Current Verdict

Keep open as a blocked identity/auth decision ticket.

Do not implement a generic disposable-email bypass as Neo substrate. If Moltbook or a similar external platform requires inbox ownership, the valid path is an operator-controlled domain/provider boundary with explicit credential handling, not throwaway-email automation.

Re-entry Gate

This ticket becomes claimable only after #9915 determines the supported Moltbook integration/auth shape:

If Moltbook identity is fully API-key/dashboard based, rewrite or close this ticket.
If inbox ownership is required, specify the operator-owned provider/domain, webhook surface, secret handling, and test boundary before implementation.
If the Moltbook path is negative ROI, close this ticket as superseded for the demo cluster.

Out of Scope

Disposable-email services as default substrate.
CAPTCHA/2FA bypass.
Platform-specific identity work before #9915 resolves the integration shape.

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 removed the agent-task:blocked label on May 28, 2026, 12:15 AM