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	9370
title	Upgrade ScrollSync Locking Mechanism
state	Closed
labels	enhancementaiarchitecture
assignees	tobiu
createdAt	Mar 7, 2026, 5:38 PM
updatedAt	Mar 7, 2026, 5:54 PM
githubUrl	https://github.com/neomjs/neo/issues/9370
author	tobiu
commentsCount	1
parentIssue	9369
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 7, 2026, 5:53 PM

Upgrade ScrollSync Locking Mechanism

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

Closed v12.1.0 enhancementaiarchitecture

tobiu commented on Mar 7, 2026, 5:38 PM

Part of Epic #9369

Refactor src/main/addon/ScrollSync.mjs to introduce an internal isCoordinating lock. When a scroll event is received from a source node, the addon must acquire the lock, mutate the target node, and release the lock only after the resulting native events have cleared. This stateful coordination prevents infinite "ping-pong" feedback loops during two-way synchronization.

tobiu added the enhancement label on Mar 7, 2026, 5:38 PM

tobiu added the ai label on Mar 7, 2026, 5:38 PM

tobiu added the architecture label on Mar 7, 2026, 5:38 PM

tobiu added parent issue #9369 on Mar 7, 2026, 5:38 PM

tobiu referenced in commit 3fd7bd0 - "feat(Grid): replace global scroll sync touch flag with granular DOM node locks (#9370, #9371)" on Mar 7, 2026, 5:52 PM

tobiu Mar 7, 2026, 5:53 PM

Input from Gemini 3.1 Pro:

✦ During implementation of the lock mechanism, we pivoted the architectural design to avoid a critical race condition.

Instead of a single global isCoordinating = true flag (which would have locked the entire application and prevented multiple grids from being scrolled simultaneously), we implemented a granular Set-based lock (this.coordinatingNodes = new Set()).

When syncTo or onScroll mutates a DOM node, it adds that specific node's id to the Set. The interceptor then only ignores incoming native scroll events if their event.target.id is currently in the Set. This allows parallel scrolling of unrelated components while still perfectly preventing ping-pong loops within synchronized pairs.

The syncTo API is now in place and uses this granular locking. I will close this ticket and #9371. We will create a separate sub-task to handle the complexities of releasing the lock during continuous momentum scrolling (rAF vs setTimeout).

tobiu closed this issue on Mar 7, 2026, 5:53 PM

tobiu assigned to @tobiu on Mar 7, 2026, 5:54 PM