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	8782
title	Prevent duplicate render loops in ServicesCanvas and HomeCanvas
state	Closed
labels	bugairefactoring
assignees	tobiu
createdAt	Jan 18, 2026, 5:43 PM
updatedAt	Jan 18, 2026, 5:49 PM
githubUrl	https://github.com/neomjs/neo/issues/8782
author	tobiu
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 18, 2026, 5:49 PM

Prevent duplicate render loops in ServicesCanvas and HomeCanvas

Closed v11.23.0/archive-v11-23-0-chunk-1 bugairefactoring

tobiu commented on Jan 18, 2026, 5:43 PM

Following the fix in TicketCanvas (#8781), we identified that ServicesCanvas and HomeCanvas in the Portal app share the same vulnerability: they do not track their animationId, making it possible to spawn parallel render loops if initGraph or resume is called multiple times or during rapid navigation.

This ticket covers the proactive refactoring of both classes to:

Convert animationId (or introduce it) as a reactive config animationId_.
Implement afterSetAnimationId to automatically cancel the previous frame/timeout.
Update the render loop to assign the frame ID to this config.
Ensure clearGraph properly nullifies the ID.

This ensures robust "single-loop" architecture across all Portal canvases.

tobiu Jan 18, 2026, 5:48 PM

Input from Gemini 3 Pro:

✦ Refactoring complete for HeaderCanvas, HomeCanvas, and ServicesCanvas.

Changes Applied:

Reactive Config: animationId converted to animationId_.

Auto-Cleanup: afterSetAnimationId hook implemented to cancel previous frames.

Render Assignment: me.animationId = requestAnimationFrame(...) added to all render loops.

Reset: clearGraph now explicitly nullifies me.animationId.

This unifies the render loop architecture across the entire Portal app, preventing any possibility of parallel/zombie loops.

tobiu Jan 18, 2026, 5:49 PM

Input from Gemini 3 Pro:

✦ Closing ticket as the fix has been implemented and pushed.