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	9369
title	[Epic] Upgrade ScrollSync for Loop-Free Two-Way Binding (Mobile & Desktop)
state	Closed
labels	enhancementepicaiarchitecture
assignees	tobiu
createdAt	Mar 7, 2026, 5:37 PM
updatedAt	Mar 7, 2026, 6:15 PM
githubUrl	https://github.com/neomjs/neo/issues/9369
author	tobiu
commentsCount	0
parentIssue	null
subIssues	9370 Upgrade ScrollSync Locking Mechanism 9371 API for Programmatic Scrolling in ScrollSync 9372 Refactor GridDragScroll to use ScrollSync API 9373 Enable Mobile Two-Way ScrollSync for Grid VerticalScrollbar 9374 Mobile UX Enhancements for Grid VerticalScrollbar (SCSS) 9375 Improve ScrollSync Lock Release Mechanism (rAF vs setTimeout) 9376 Add .neo-has-touch capability class and enhance Mobile Grid Scrollbar 9377 Define `--grid-scrollbar-touch-width` variable across all themes 9378 Extract desktop grid scrollbar width into a CSS variable 9379 Mobile Scrollbar UX: Increase touch width to 40px and theme thumb colors
subIssuesCompleted	10
subIssuesTotal	10
blockedBy	[]
blocking	[]
closedAt	Mar 7, 2026, 6:15 PM

[Epic] Upgrade ScrollSync for Loop-Free Two-Way Binding (Mobile & Desktop)

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

Closed v12.1.0 enhancementepicaiarchitecture

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

The current ScrollSync.mjs architecture relies on blind native scroll event listeners. To prevent infinite "ping-pong" feedback loops, it explicitly disables two-way synchronization on touch devices (twoWay: Neo.config.hasMouseEvents). This breaks the UX on mobile for virtualized components (like Grids with custom scrollbars), preventing users from grabbing and scrubbing the scrollbar. Furthermore, it conflicts with programmatic scrolling addons like GridDragScroll which continuously mutate the DOM during momentum animations.

This epic proposes upgrading ScrollSync to act as a stateful coordinator. By implementing an internal locking mechanism (isCoordinating), it can safely apply bidirectional scroll updates across multiple nodes and programmatic sources without triggering native event feedback loops.

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

tobiu added the epic label on Mar 7, 2026, 5:37 PM

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

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

tobiu cross-referenced by #9370 on Mar 7, 2026, 5:38 PM

tobiu added sub-issue #9370 on Mar 7, 2026, 5:38 PM

tobiu cross-referenced by #9371 on Mar 7, 2026, 5:39 PM

tobiu added sub-issue #9371 on Mar 7, 2026, 5:39 PM

tobiu cross-referenced by #9372 on Mar 7, 2026, 5:39 PM

tobiu added sub-issue #9372 on Mar 7, 2026, 5:39 PM

tobiu cross-referenced by #9373 on Mar 7, 2026, 5:39 PM

tobiu added sub-issue #9373 on Mar 7, 2026, 5:39 PM

tobiu cross-referenced by #9374 on Mar 7, 2026, 5:39 PM

tobiu added sub-issue #9374 on Mar 7, 2026, 5:39 PM

tobiu cross-referenced by #9375 on Mar 7, 2026, 5:54 PM

tobiu added sub-issue #9375 on Mar 7, 2026, 5:54 PM

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

tobiu cross-referenced by #9376 on Mar 7, 2026, 6:10 PM

tobiu added sub-issue #9376 on Mar 7, 2026, 6:10 PM

tobiu closed this issue on Mar 7, 2026, 6:15 PM

tobiu cross-referenced by #9377 on Mar 7, 2026, 6:19 PM

tobiu added sub-issue #9377 on Mar 7, 2026, 6:19 PM

tobiu cross-referenced by #9378 on Mar 7, 2026, 6:26 PM

tobiu added sub-issue #9378 on Mar 7, 2026, 6:26 PM

tobiu cross-referenced by #9379 on Mar 7, 2026, 6:56 PM

tobiu added sub-issue #9379 on Mar 7, 2026, 6:57 PM

tobiu cross-referenced by #9380 on Mar 7, 2026, 7:25 PM