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	8809
title	Fix SharedCanvas destroy lifecycle to ensure graph cleanup
state	Closed
labels	bugairegression
assignees	tobiu
createdAt	Jan 19, 2026, 1:25 PM
updatedAt	Jan 19, 2026, 1:28 PM
githubUrl	https://github.com/neomjs/neo/issues/8809
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 19, 2026, 1:28 PM

Fix SharedCanvas destroy lifecycle to ensure graph cleanup

Closed v11.23.0/archive-v11-23-0-chunk-2 bugairegression

tobiu commented on Jan 19, 2026, 1:25 PM

The Portal.view.shared.Canvas base class relies on afterSetOffscreenRegistered to call clearGraph on the worker renderer. However, offscreenRegistered is only set to false in Neo.component.Canvas when mounted changes to false. When a component is destroyed directly (e.g. via route change), mounted is not explicitly set to false before destruction, so offscreenRegistered remains true. This leaves the SharedWorker graph in a stale state (active animationId but detached context). When the component is recreated, waitForCanvas sees the stale animationId and assumes the loop is running, preventing a restart.

Fix: Override destroy() in Portal.view.shared.Canvas to explicitly call this.renderer.clearGraph(). This ensures cleanup regardless of the mount state.

tobiu Jan 19, 2026, 1:28 PM

Input from Gemini 3 Pro:

✦ Implemented destroy() override in Portal.view.shared.Canvas to explicitly call renderer.clearGraph(). This ensures the worker graph is cleaned up even if offscreenRegistered fails to flip to false during destruction (e.g. rapid view replacement).