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	8565
title	Scope timeline item IDs to Ticket ID to prevent stale rects on switch
state	Closed
labels	bugai
assignees	tobiu
createdAt	Jan 12, 2026, 12:37 AM
updatedAt	Jan 12, 2026, 12:40 AM
githubUrl	https://github.com/neomjs/neo/issues/8565
author	tobiu
commentsCount	1
parentIssue	8398
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 12, 2026, 12:40 AM

Scope timeline item IDs to Ticket ID to prevent stale rects on switch

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

Closed v11.20.0 bugai

tobiu commented on Jan 12, 2026, 12:37 AM

When switching between tickets that happen to have the same number of timeline events, TimelineCanvas sometimes renders the "old" event positions.

Root Cause: The timeline items use generic IDs like timeline-1, timeline-2. When switching tickets, if the Component is reused, the new HTML has the same IDs. TimelineCanvas calls waitForDomRect. If the DOM update hasn't happened yet (the old ticket HTML is still present), waitForDomRect finds the old elements (same IDs) immediately and returns stale rects.

Solution: Scope the timeline item IDs to the Ticket ID. Instead of timeline-1, use timeline-{ticketId}-1.

This ensures that when TimelineCanvas receives new data (for Ticket B), it looks for timeline-{ticketB}-1. These elements do not exist in the old DOM (Ticket A). waitForDomRect will correctly wait until the new HTML is mounted.

Changes:

Modify apps/portal/view/news/tickets/Component.mjs to include me.record.id in bodyId and generated timeline event IDs.

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

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

tobiu referenced in commit d90b171 - "fix: Scope timeline item IDs to Ticket ID to prevent stale rects (#8565)" on Jan 12, 2026, 12:39 AM

tobiu assigned to @tobiu on Jan 12, 2026, 12:39 AM

tobiu Jan 12, 2026, 12:39 AM

Input from Gemini 3 Pro:

✦ I have scoped the timeline item IDs to the Ticket ID.

Changes:

Modified apps/portal/view/news/tickets/Component.mjs to generate IDs in the format timeline-{ticketId}-{index} instead of timeline-{index}.

This applies to both the body item (timeline-{ticketId}-0) and all parsed timeline events.

This ensures that when TimelineCanvas waits for DOM elements after a ticket switch, it looks for new IDs that correspond to the new ticket. If the DOM update is pending, waitForDomRect will correctly wait until the new elements are mounted, preventing the use of stale rects from the previous ticket's view.

tobiu added parent issue #8398 on Jan 12, 2026, 12:40 AM

tobiu closed this issue on Jan 12, 2026, 12:40 AM