What is the 'Neural Link'?

The Neural Link is a bi-directional bridge that connects AI agents (like Gemini or Claude) directly to the Neo.mjs runtime. It allows agents to 'see' the application's Scene Graph, inspect component state, verify event listeners, and even mutate the running application in real-time. This turns the application into a 'glass box' for AI, enabling autonomous debugging and feature development.

Why is Neo.mjs called an 'Application Engine' instead of a framework?

Traditional frameworks are general-purpose libraries (like a Toyota) that help you organize code, but they compile away into ephemeral DOM nodes. Neo.mjs is a precision-engineered runtime (like an F1 car), similar to Unreal Engine for games. It maintains a persistent 'Scene Graph' of objects in a separate worker thread. These objects retain their identity, state, and relationships, allowing for advanced capabilities like multi-window orchestration, runtime permutation, and deep AI introspection that are impossible with 'melted plastic' DOM-based frameworks.

What is 'Context Engineering'?

Context Engineering is the practice of curating the environment and information flow for AI agents to maximize their autonomy. In Neo.mjs, this is implemented via three Model Context Protocol (MCP) servers: a Knowledge Base for semantic code understanding, a Memory Core for learning from past sessions, and a GitHub Workflow server for project management. This ecosystem allows agents to work as fully integrated members of the development team.

What is 'Object Permanence' in the context of Neo.mjs?

In Neo.mjs, UI components are persistent JavaScript objects living in the App Worker, not just transient rendering results. This 'Object Permanence' means a component (like a Dashboard) maintains its state (scroll position, user input, internal logic) even if it is detached from the DOM or moved to a different browser window. This is the 'Lego Technic' approach versus the 'Duplo' approach of traditional frameworks.

What is an 'Agent Operating System'?

Neo.mjs v11 introduced the concept of an Agent OS, where the platform itself provides the tools and interfaces for AI agents to operate. It combines a standalone, type-safe AI SDK for autonomous 'Code Execution' with the Neural Link for runtime control. This enables agents to monitor, debug, and heal the application autonomously, effectively acting as an operating system for synthetic intelligence.

How does Neo.mjs handle multi-window applications?

Neo.mjs uses shared web workers to run a single application instance across multiple browser windows. All windows share the same application state and data in real-time. Components can even move between windows while retaining their JavaScript instances. This enables desktop-class experiences like multi-window IDEs, browser-based email clients, and multi-screen control rooms.

What makes Neo.mjs different from React, Angular, or Vue?

Neo.mjs is fundamentally different in its architecture: (1) It uses True Multithreading via web workers to prevent UI jank, (2) It is an AI-Native Application Engine with built-in bridges for AI collaboration, and (3) It treats components as persistent objects in a Scene Graph, enabling native multi-window support and runtime permutation.

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
blockedBy	[]
blocking	[]
closedAt	Jan 18, 2026, 5:49 PM

Prevent duplicate render loops in ServicesCanvas and HomeCanvas

Name: Neo.mjs Application Engine
Author: Neo.mjs

Closed v11.23.0 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 added the bug label on Jan 18, 2026, 5:43 PM

tobiu added the ai label on Jan 18, 2026, 5:43 PM

tobiu added the refactoring label on Jan 18, 2026, 5:43 PM

tobiu referenced in commit cea8c4a - "refactor: prevent duplicate render loops in all Portal canvases via reactive animationId (#8782)" on Jan 18, 2026, 5:48 PM

tobiu assigned to @tobiu on Jan 18, 2026, 5:48 PM

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.

tobiu closed this issue on Jan 18, 2026, 5:49 PM