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.

Neo.mjs - Self-Evolving Software Organism

Frontmatter

title	>-
author	neo-opus-grace
state	Merged
createdAt	Jun 4, 2026, 3:01 AM
updatedAt	Jun 4, 2026, 3:04 AM
closedAt	Jun 4, 2026, 3:04 AM
mergedAt	Jun 4, 2026, 3:04 AM
branches	`dev` ← `agent/12461-wake-activate-foreground`
url	https://github.com/neomjs/neo/pull/12463

Merged

neo-opus-grace commented on Jun 4, 2026, 3:01 AM

Authored by Claude Opus 4.8 (Claude Code). Session 3ecb40bf-bfef-40b1-8693-a8aae5afa1b7.

Resolves #12462 Refs #11822 Refs #12440

Restores the robust tell application "<App>" to activate foregrounding that #11822 removed for --user-data-dir harness instances, then sets frontmost on the resolved instance pid for precision. #11822 swapped activate for set frontmost of unix id alone, which cannot switch between two same-bundle Electron instances from the headless daemon — so #12424's frontmost guard hard-drops the wake whenever a same-bundle sibling holds the foreground. The Neo instance lost 16 wakes on 06-03 + 21 on 06-04 to the default Claude this way.

FAIR-band: under-target (@neo-opus-grace; bug fix unblocking the swarm's own wake delivery).

Evidence: L1 (static — restores the empirically-proven pre-#11822 activate mechanism that delivered 740 wakes on 06-03; host osascript probes confirm activate+set frontmost raises the target and AXRaise de-raises it) → L4 (live daemon delivery) observed post-deploy in bridge.log. No blocking residual — this restores known-good behavior.

What shipped (`ai/daemons/bridge/daemon.mjs`)

Each poll-re-activate iteration on the instance path now runs tell application "<App>" to activate (robust bundle foreground — reclaims focus from a same-bundle sibling, works from the headless daemon) → set frontmost of (process whose unix id is <pid>) (instance disambiguation). Single-instance / no---user-data-dir path keeps activate only (unchanged). AXRaise is NOT used (empirically de-raises).

Deltas from ticket

None — implements the ticket's stated fix exactly.

Test Evidence

node --check passes. Host osascript matrix (Neo 92897 vs default Claude 91267): activate+set frontmost → PASS; set frontmost alone → contention-sensitive; AXRaise → FAIL (de-raises). Daemon-context confirmation is post-deploy (bridge.log): WAKE_SUB:84dfc4da shows Delivered rather than 91267 != 92897 drops.

Post-Merge Validation

After daemon restart, the Neo instance's wakes deliver while the default Claude sibling is frontmost.
No regression for Codex / Antigravity (different bundles).

Deploy

Restart the bridge daemon (merge + pull + restart, or git checkout agent/12461-wake-activate-foreground -- ai/daemons/bridge/daemon.mjs in the deployment clone + restart) — it picks up the new code on next start.

🖖