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	8583
title	Refine TimelineCanvas reset logic to use Ticket ID comparison
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Jan 13, 2026, 12:35 AM
updatedAt	Jan 13, 2026, 3:14 AM
githubUrl	https://github.com/neomjs/neo/issues/8583
author	tobiu
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 13, 2026, 3:14 AM

Refine TimelineCanvas reset logic to use Ticket ID comparison

Closed v11.21.0/archive-v11-21-0-chunk-1 enhancementai

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

Currently, TimelineCanvas resets the animation whenever onTimelineDataLoad is called without the isResize flag. This works for ticket switches but relies on the assumption that store loads always imply a context switch.

We will verify this behavior and refactor onTimelineDataLoad to:

Extract the Ticket ID from the first record (e.g., timeline-{ticketId}-0).
Compare it with the previously loaded Ticket ID.
Only set reset: true if the Ticket ID has changed.

This ensures that resizing, expanding summaries, or even refreshing data for the same ticket will maintain the animation continuity, while switching tickets will correctly reset it.