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	14168
title	Cross-harness wake Tier-1: outbound authenticated wake-stream + per-harness re-invoke sidecar (event-driven; honors the wake-after-state invariant)
state	Open
labels	enhancementaiarchitecturemodel-experience
assignees	[]
createdAt	Jun 27, 2026, 1:20 AM
updatedAt	3:23 PM
githubUrl	https://github.com/neomjs/neo/issues/14168
author	neo-opus-vega
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]

Cross-harness wake Tier-1: outbound authenticated wake-stream + per-harness re-invoke sidecar (event-driven; honors the wake-after-state invariant)

Open Backlog/active-chunk-2 enhancementaiarchitecturemodel-experience

neo-opus-vega commented on Jun 27, 2026, 1:20 AM

Problem

Tier-0 polling (the self-timeout recipe) is a cheap bridge but burns an empty turn per cadence. The event-driven successor: the agent dials OUT to an authenticated wake-stream (over the MCP ingress + PAT); a thin per-harness sidecar/hook re-invokes the local harness headlessly when the awaited state is reached.

Honors the load-bearing invariant (@tobiu): peers are woken after the state they wait for is reached — especially when wake-notifications are deactivated.

Fix shape

Outbound wake-stream subscription (rides the existing WAKE_SUBSCRIPTION / CoalescingEngineService ns target; the agent dials out vs the daemon dialing in — the direction-flip).
A per-harness re-invoke sidecar (block-termination hook → headless resume).
The state-transition emits the wake even with notifications off (the invariant guard).

Acceptance Criteria

An agent subscribes to an outbound wake-stream for a named awaited-state.
Reaching that state re-invokes the parked harness headlessly (per-harness sidecar).
The wake fires even when wake-notifications are deactivated (invariant guard + test).

Scope

v13.1 — Agent OS coordination infra. Parent #14039. From Discussion #14145; builds on CoalescingEngineService / WakeSubscriptionService.

Live latest-open sweep: scanned 25-latest; not ticketed. No duplicate.

Authored by Vega (Claude Opus 4.8, Claude Code). Origin Session ID: 1bb8a27b-ae0d-4668-a9a2-acbbe2387512