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	8563
title	Prevent race condition in TimelineCanvas by making sections store update optional
state	Closed
labels	bugairefactoring
assignees	tobiu
createdAt	Jan 12, 2026, 12:19 AM
updatedAt	Jan 12, 2026, 12:27 AM
githubUrl	https://github.com/neomjs/neo/issues/8563
author	tobiu
commentsCount	1
parentIssue	8398
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 12, 2026, 12:27 AM

Prevent race condition in TimelineCanvas by making sections store update optional

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

Closed v11.20.0 bugairefactoring

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

Portal.view.shared.content.Component automatically updates the sections store with extracted headlines in modifyMarkdown. Portal.view.news.tickets.Component extends this class but overrides the sections store with Timeline Data instead.

This creates a race condition:

super.modifyMarkdown() runs and pushes Headlines to the store.
TimelineCanvas (listening to the store) tries to render these Headlines as timeline events, causing glitches (or successfully finding a stray element and rendering a bogus graph).
Tickets.Component finishes parsing and pushes Timeline Data to the store.
TimelineCanvas updates correctly.

To fix this, we need to make the store update in the base class optional.

Proposed Change:

Add updateSectionsStore: true config to Portal.view.shared.content.Component.
Wrap the store update in modifyMarkdown with if (this.updateSectionsStore).
Set updateSectionsStore: false in Portal.view.news.tickets.Component.

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

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

tobiu added the refactoring label on Jan 12, 2026, 12:19 AM

tobiu referenced in commit 605635a - "fix: Prevent race condition in TimelineCanvas by making sections store update optional (#8562, #8563)" on Jan 12, 2026, 12:26 AM

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

tobiu Jan 12, 2026, 12:27 AM

Input from Gemini 3 Pro:

✦ I have implemented the fix to prevent the "sections" store race condition.

Changes:

Shared Component: Added updateSectionsStore config (default true) to apps/portal/view/shared/content/Component.mjs. Modified modifyMarkdown to only update the store if this flag is true.

Tickets Component: Set updateSectionsStore: false in apps/portal/view/news/tickets/Component.mjs. This prevents the base class from pushing Headlines to the store, allowing the subclass to exclusively manage the store with Timeline data.

Tickets Component: Added construct to initialize contentComponentId in the state provider, fixing the underlying ID resolution issue for TimelineCanvas.

This ensures TimelineCanvas only receives valid Timeline updates and no longer gets "flashed" with headline data during navigation.

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

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