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	8582
title	Fix TimelineCanvas sync drift by adding debounced final alignment check
state	Closed
labels	bugai
assignees	tobiu
createdAt	Jan 13, 2026, 12:18 AM
updatedAt	Jan 13, 2026, 12:28 AM
githubUrl	https://github.com/neomjs/neo/issues/8582
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 13, 2026, 12:28 AM

Fix TimelineCanvas sync drift by adding debounced final alignment check

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

Closed v11.21.0 bugai

tobiu commented on Jan 13, 2026, 12:18 AM

During the expand/collapse animation of the ticket summary, onResize fires multiple times as expected. However, the canvas nodes often settle at an intermediate position, misaligned with the final DOM elements.

This happens because waitForDomRect captures the element positions during the transition. If the CSS animation finishes after the last ResizeObserver event, or if the browser layout isn't fully settled when the last resize handler runs, the canvas retains the stale coordinates.

Resolution:

Add ensureFinalAlignment to static delayable in TimelineCanvas.mjs (debounce: 100ms).
Inside ensureFinalAlignment, call this.onTimelineDataLoad(this.lastRecords, true).
Inside onResize, call this.ensureFinalAlignment() in addition to the immediate update.

This guarantees a final synchronization pass after the resize activity stabilizes.

tobiu added the bug label on Jan 13, 2026, 12:18 AM

tobiu added the ai label on Jan 13, 2026, 12:18 AM

tobiu referenced in commit d6956bd - "fix(TimelineCanvas): set alignment debounce to 200ms for optimal sync (#8582)" on Jan 13, 2026, 12:27 AM

tobiu assigned to @tobiu on Jan 13, 2026, 12:28 AM

tobiu Jan 13, 2026, 12:28 AM

Input from Gemini 3 Pro:

✦ I have fixed the alignment drift by implementing a robust, debounced final check.

The Fix:

Intermediate State: The waitForDomRect method inside onTimelineDataLoad works correctly, but during a CSS animation (like expanding/collapsing the summary), it captures the current animating position, not the final one.

Debounced Alignment: I introduced ensureFinalAlignment as a delayable method with a 200ms debounce.

This method re-triggers onTimelineDataLoad with the cached records.

Because it is debounced, it waits until the flurry of onResize events settles.

The 200ms delay ensures we catch the state after the CSS transition has fully completed (t > 300ms total from start of animation), while avoiding excessive visual lag.

This ensures the canvas nodes snap to their correct final positions once the UI stabilizes.

tobiu closed this issue on Jan 13, 2026, 12:28 AM