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	8781
title	Fix duplicate TicketCanvas animation loops via reactive animationId
state	Closed
labels	bugai
assignees	tobiu
createdAt	Jan 18, 2026, 5:33 PM
updatedAt	Jan 18, 2026, 5:37 PM
githubUrl	https://github.com/neomjs/neo/issues/8781
author	tobiu
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 18, 2026, 5:37 PM

Fix duplicate TicketCanvas animation loops via reactive animationId

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

Closed v11.23.0 bugai

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

The TicketCanvas singleton (Canvas Worker) fails to track its animationId correctly, causing it to remain null even after an animation loop starts. This leads to updateGraphData spawning a new, parallel render loop every time the timeline data refreshes (e.g., navigating between tickets), resulting in visual glitches and performance degradation.

This ticket refactors TicketCanvas.mjs to:

Convert the animationId class field into a reactive config: animationId_.
Implement afterSetAnimationId to handle cleanup (canceling the previous frame) automatically when the ID changes.
Ensure the render loop correctly assigns the new frame ID to this.animationId.
Ensure clearGraph properly nullifies animationId to stop the loop.

This ensures only one render loop is ever active at a time.

tobiu added the bug label on Jan 18, 2026, 5:33 PM

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

tobiu referenced in commit 637e76c - "fix: TicketCanvas prevent duplicate render loops via reactive animationId (#8781)" on Jan 18, 2026, 5:36 PM

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

tobiu Jan 18, 2026, 5:37 PM

Input from Gemini 3 Pro:

✦ Refactoring complete.

Reactive Config: animationId is now animationId_, a reactive config.

Auto-Cleanup: afterSetAnimationId now automatically cancels the previous frame (or timeout) whenever the ID changes.

Render Loop: The render method now correctly assigns me.animationId to the result of requestAnimationFrame (or setTimeout), ensuring the loop is tracked.

Cleanup: clearGraph now sets me.animationId = null to stop the loop when unmounting.

This guarantees that a new loop cannot start without killing the old one, resolving the duplicate render issue.

tobiu Jan 18, 2026, 5:37 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:37 PM

tobiu cross-referenced by #8782 on Jan 18, 2026, 5:43 PM