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	12219
title	Make tickets controller deep-link + default-route lazy-aware
state	Closed
labels	enhancementaiperformance
assignees	neo-opus-ada
createdAt	May 30, 2026, 7:27 PM
updatedAt	Jun 1, 2026, 6:12 PM
githubUrl	https://github.com/neomjs/neo/issues/12219
author	neo-opus-ada
commentsCount	4
parentIssue	12204
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[x] 12305 Adopt chunked lazy nav for portal pulls (store + controller + theme), [x] 12218 Opt-in load-on-folder-expand for the shared portal TreeList
blocking	[]
closedAt	Jun 1, 2026, 6:12 PM

Make tickets controller deep-link + default-route lazy-aware

Closed Backlog/active-chunk-16 enhancementaiperformance

neo-opus-ada commented on May 30, 2026, 7:27 PM

Context

Part of epic #12207 (Track B; #11372 Phase 2). MainContainerController.getDefaultRouteId + onRouteItem/expandAndScrollToItem iterate the WHOLE store assuming all nodes are present — they misbehave under partial (lazy) load.

The Fix

Make them resolve a target id to its group/chunk (via ADR 0004's _index.json id→path map) and pre-fetch that chunk before the node exists. Required for lazy mode to work with deep links and the default route. Decide whether _index.json carries the parent-folder, or a separate node-index is needed.

Acceptance Criteria

Deep-links + the default route resolve correctly under lazy load (target chunk pre-fetched before navigation).

Epic #12207; #11372 Phase 2. Depends on the lazy folder-load (sub 13).

tobiu referenced in commit 341e7ec - "fix(portal): deep-link tab activation + PR-view timeline theming (#12300) (#12301) on Jun 1, 2026, 2:43 PM

tobiu referenced in commit 43cf654 - "fix(portal): pulls chunked lazy nav — store + controller + theme vars (#12305) (#12307) on Jun 1, 2026, 6:14 PM

Make tickets controller deep-link + default-route lazy-aware

Context

The Fix

Acceptance Criteria

Related