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	12402
title	Post-merge L3 validation: live 2-instance Claude sibling wake delivery (#11822 AC7/AC9)
state	Open
labels	aiarchitecturemodel-experience
assignees	neo-opus-ada
createdAt	Jun 3, 2026, 2:18 AM
updatedAt	Jun 7, 2026, 3:37 PM
githubUrl	https://github.com/neomjs/neo/issues/12402
author	neo-opus-ada
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]

Post-merge L3 validation: live 2-instance Claude sibling wake delivery (#11822 AC7/AC9)

Open Backlog/active-chunk-17 aiarchitecturemodel-experience

neo-opus-ada commented on Jun 3, 2026, 2:18 AM

Context

PR #12399 (Resolves #11822) ships instance-addressable wake routing for two same-bundle Claude.app harnesses. It merges with #11822's AC7/AC9 explicitly annotated [L3-deferred — operator handoff needed] — the live two-instance proof needs two running Desktop instances and is operator-run, so it cannot complete pre-merge. Since Resolves #11822 auto-closes the parent, this ticket preserves the L3 validation so it is not lost from active queues. This is also the operator's live 3-way (Claude + GPT + sibling) A2A-with-wakeups demo.

The Validation (operator-run)

With two Claude.app instances running — the default maintainer + the @neo-claude-opus instance launched with NEO_AGENT_IDENTITY=neo-claude-opus and a distinct --user-data-dir:

AC7: a wake for the @neo-claude-opus subscription lands in the neo-claude-opus instance over ≥2 controlled cycles.
Wrong-instance probe: a wake targeting the neo-claude-opus userDataDir never lands in the default instance (fail-closed proven live).
Confirm the 2nd instance's MAIN process carries --user-data-dir (the resolver prefers it; the helper→ppid fallback covers the alternative if not).
AC9: artifact comment on #11812 with the live result.

Prerequisites

#12399 merged.
bridge-daemon restarted (to load the instance-routing code).
2nd harness launched with NEO_AGENT_IDENTITY=neo-claude-opus.
@neo-claude-opus seeded into the live graph.

Implements the deferred L3 of #11822 / PR #12399.
Parent epic #11812 (AC12 live-proof).

Post-merge L3 validation: live 2-instance Claude sibling wake delivery (#11822 AC7/AC9)

Context

The Validation (operator-run)

Prerequisites

Related