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	14167
title	Cross-harness wake Tier-0: self-timeout re-check recipe (zero-server bridge for hybrid/cloud; works on today''s harnesses)
state	Open
labels	enhancementaiarchitecturemodel-experience
assignees	[]
createdAt	Jun 27, 2026, 1:20 AM
updatedAt	Jul 6, 2026, 3:22 PM
githubUrl	https://github.com/neomjs/neo/issues/14167
author	neo-opus-vega
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]

Cross-harness wake Tier-0: self-timeout re-check recipe (zero-server bridge for hybrid/cloud; works on today's harnesses)

Open Backlog/active-chunk-2 enhancementaiarchitecturemodel-experience

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

Problem

The macOS GUI wake-daemon does not work for a cloud deployment with operators on mixed OSes / harnesses (Claude Code / Codex / Antigravity). A parked agent waiting on a peer-event currently stalls. (Discussion #14145.)

Fix shape (Tier-0 — zero-server, zero-clone)

A parked agent schedules its own re-check instead of stopping; on wake it queries Memory Core for the named awaited-event → acts or re-schedules; bounded by a max-wait budget.
Per-harness: Claude Code ScheduleWakeup / /loop (native); Codex OS-cron codex resume (no native scheduler); Antigravity Scheduled Tasks.
Config + docs (deployment operators can set it up without cloning neo).

Acceptance Criteria

A parked agent re-checks MC for its named awaited-event on cadence, bounded by a max-wait budget.
Recipe documented per-harness (Claude Code native; Codex OS-cron; Antigravity tasks).
No server change, no neo clone required.

Scope

v13.1 — Agent OS coordination infra, pulled into v13.1 (v13.2 swings to the harness/fleet pivot). Parent #14039. From Discussion #14145.

Live latest-open sweep: scanned 25-latest; wake is Discussion #14145, not yet ticketed. No duplicate.

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