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	12419
title	Ticket C — macOS-Electron parent-chain-walk fallback for instance-address discovery
state	Closed
labels	enhancementaiarchitecture
assignees	neo-gpt
createdAt	Jun 3, 2026, 5:49 AM
updatedAt	Jun 5, 2026, 3:32 PM
githubUrl	https://github.com/neomjs/neo/issues/12419
author	neo-opus-ada
commentsCount	1
parentIssue	12416
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[x] 12422 Ticket B2 — volatile HarnessPresence registry (state∪address) + addressType dispatch + staleness
blocking	[]
closedAt	Jun 5, 2026, 3:32 PM

Ticket C — macOS-Electron parent-chain-walk fallback for instance-address discovery

Closed v13.0.0/archive-v13-0-0-chunk-15 enhancementaiarchitecture

neo-opus-ada commented on Jun 3, 2026, 5:49 AM

Part of Epic #12416 (graduated from Discussion #12412). Lowest priority — conditional fallback only.

Context (OQ1 V-B-A by @neo-opus-grace, Discussion #12412 comment 17159985)

A sandboxed stdio MCP server CAN read parent argv via ps (not OS-sandboxed; resolveInstancePid already does this in prod). BUT the direct parent is a Claude Desktop helper, not the main app — --user-data-dir lives on the main executable. So a macOS-Electron fallback must walk the parent-pid chain (helper→main) from the server's own boot pid, reusing resolveInstancePid's helper-walk. Explicitly NOT portable — dies under cloud-SSE (no Electron parent).

Scope

When Ticket B's env-envelope lacks an instanceAddress AND running under macOS-Electron, attempt a parent-chain-walk from the server's boot pid (reuse resolveInstancePid) to discover --user-data-dir.
Fallback only, never the primary path. Cloud-SSE / no-Electron-parent → graceful no-op.

Acceptance Criteria

AC1: macOS-Electron parent-chain-walk discovers --user-data-dir from the server boot pid (helper→main), reusing resolveInstancePid.
AC2: used ONLY when the envelope lacks instanceAddress; never overrides an explicit envelope value.
AC3: graceful no-op under cloud-SSE / no Electron parent.
AC4: unit coverage with a mock ps snapshot exercising the helper→main chain.

Epic #12416; Discussion #12412 OQ1 (@neo-opus-grace V-B-A, comment 17159985); resolveInstancePid (#12399).

tobiu referenced in commit 56a082f - "feat(memory-core): discover wake instance address from parent chain (#12419) (#12563)" on Jun 5, 2026, 3:32 PM

tobiu closed this issue on Jun 5, 2026, 3:32 PM

Ticket C — macOS-Electron parent-chain-walk fallback for instance-address discovery

Context (OQ1 V-B-A by @neo-opus-grace, Discussion #12412 comment 17159985)

Scope

Acceptance Criteria

Related