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	13381
title	Refresh Agent Harness workflow Electron route map
state	Closed
labels	bugdocumentationaiarchitecturemodel-experience
assignees	neo-gpt
createdAt	Jun 15, 2026, 8:40 PM
updatedAt	Jun 15, 2026, 9:29 PM
githubUrl	https://github.com/neomjs/neo/issues/13381
author	neo-gpt
commentsCount	0
parentIssue	144
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 15, 2026, 9:29 PM

Refresh Agent Harness workflow Electron route map

Closed v13.1.0/archive-v13-1-0-chunk-3 bugdocumentationaiarchitecturemodel-experience

neo-gpt commented on Jun 15, 2026, 8:40 PM

Context

The Agent Harness session-entry workflow is intentionally short and read-on-demand: .agents/workflows/agent-harness.md sends fresh sessions through ADR 0020, Project board 13, and the target work item. During the 2026-06-15 planning pass, the live issue graph changed under that workflow:

#13377 now exists as the Electron shell umbrella under neomjs/neo-agent-brain#144.
#13033 is now the first build-root/topology-spike leaf under #13377.
.agents/workflows/agent-harness.md Step 3 still says: Electron shell/build-root work routes through neomjs/neo#13033.

That was correct before the new umbrella existed. It is now stale enough to misroute future sessions into treating a leaf as the canonical Electron route.

Live latest-open sweep: checked latest 20 open issues immediately before filing at 2026-06-15T18:50Z. Closest matches were neomjs/neo-agent-institution#7, neomjs/neo#13033, and neomjs/neo-agent-brain#144; no equivalent workflow-route cleanup leaf found. Exact source/local sweep over .agents, learn, and resources/content found prior neomjs/neo#13250 workflow staleness history but no current neomjs/neo-agent-institution#7 route-map ticket. Native A2A in-flight claim sweep could not be run because this Codex surface exposes no list_messages / add_message tools; GitHub state and source are the available authority.

The Problem

The workflow's purpose is to remove cold-entry archaeology. A stale hardcoded Electron pointer defeats that purpose: a future agent can follow the workflow, see neomjs/neo#13033 as the Electron route, and miss the accepted umbrella/sub-issue shape where #13377 owns shell packaging/hosting/distribution and #13033 is only the first spike leaf.

This is a route-map bug, not a new Electron implementation scope.

The Architectural Reality

neomjs/neo-agent-brain#144 remains the Agent Harness parent epic and live decomposition root.
neomjs/neo-agent-institution#7 is now natively parented under neomjs/neo-agent-brain#144 and owns Electron shell / packaging / main-process Agent OS hosting / distribution, explicitly excluding multi-window choreography.
neomjs/neo#13033 is natively parented under neomjs/neo-agent-institution#7 and remains Ada's first build-root/topology-spike leaf.
.agents/workflows/agent-harness.md is the session-entry surface; it should point to live routing anchors and avoid duplicating full epic bodies.
ADR 0020 already says neomjs/neo#13033 carries the topology spike, so this ticket should only change ADR wording if needed to prevent a conflicting entry contract.

The Fix

One narrow PR:

Update .agents/workflows/agent-harness.md Step 3 so Electron shell work routes through neomjs/neo-agent-institution#7, with neomjs/neo#13033 named as the first build-root/topology-spike leaf.
Keep the anti-duplicate instruction: do not file duplicate Electron-support tickets unless live state shows disjoint scope, supersession, or explicit handoff.
Check learn/agentos/decisions/0020-agent-harness-concept.md for conflicting session-intake wording. Update only if the ADR currently contradicts the workflow route-map; otherwise leave ADR 0020 stable.

Contract Ledger Matrix

Target Surface	Source of Authority	Proposed Behavior	Fallback	Docs	Evidence
`.agents/workflows/agent-harness.md` Step 3	neomjs/neo-agent-brain#144 live issue graph + neomjs/neo-agent-institution#7 / neomjs/neo#13033 parent-child state	Route Electron shell work through neomjs/neo-agent-institution#7 and identify neomjs/neo#13033 as the first build-root/topology-spike leaf	If neomjs/neo-agent-institution#7 is closed/superseded later, Step 3 keeps its existing live-state/supersession escape hatch	Inline workflow text	Static grep + cold-read check
ADR 0020 session-intake / shell wording	ADR 0020 + this ticket	Remains non-conflicting with the workflow's route-map; updated only if it still presents neomjs/neo#13033 as the full Electron route	If unchanged, PR body explains why ADR 0020 is concept-stable and workflow owns live route shorthand	ADR text if changed	Static grep + diff review

Decision Record impact

Aligned-with ADR 0020. This does not change the Electron decision, shell boundary, Agent Harness pillars, or guardrails; it keeps the operational entry workflow aligned with the current issue graph.

Acceptance Criteria

.agents/workflows/agent-harness.md no longer presents neomjs/neo#13033 as the whole Electron shell/build-root route.
The workflow names neomjs/neo-agent-institution#7 as the Electron shell route and neomjs/neo#13033 as its first build-root/topology-spike leaf.
The workflow remains compact and pointer-based; it does not duplicate neomjs/neo-agent-institution#7 or neomjs/neo#13033 bodies.
ADR 0020 is checked for conflicting route-map wording and either updated or explicitly left stable with rationale in the PR body.
Static verification includes grep evidence for #13033, #13377, and the stale phrase Electron shell/build-root work routes through neomjs/neo#13033.

Out of Scope

Implementing the Electron shell.
Creating new Electron child tickets.
Rewriting neomjs/neo-agent-brain#144, neomjs/neo-agent-institution#7, or neomjs/neo#13033 bodies.
Changing lead-role rotation, Project board structure, or workflow convention rules.
Editing .agents/skills/** or always-loaded AGENTS substrate.

Avoided Traps / Gold Standards Rejected

Use neomjs/neo-agent-institution#7 as the implementation ticket — rejected because the edit is a tiny workflow-route cleanup and neomjs/neo-agent-institution#7 is an umbrella epic.
Create duplicate Electron support tickets — rejected; neomjs/neo#13033 remains the first implementation leaf under neomjs/neo-agent-institution#7.
Copy the full Electron plan into the workflow — rejected because workflows are entry sequences, not plan mirrors.

Parent: neomjs/neo-agent-brain#144 Related: neomjs/neo-agent-institution#7, neomjs/neo#13033, neomjs/neo#13250

Release classification: post-release (Agent Harness planning hygiene; not v13-release-blocking).

Origin Session ID: current @neo-gpt Codex Desktop goal session, 2026-06-15.

Handoff Retrieval Hints: search .agents/workflows/agent-harness.md for Electron shell/build-root; inspect neomjs/neo-agent-institution#7 and neomjs/neo#13033 native parent-child state; review neomjs/neo-agent-brain#144 checkpoint 2026-06-15T18:20Z.