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	9393
title	E2E: Implement GridRowScrollPinning via CSS Variables
state	Closed
labels	enhancementaiarchitecturegrid
assignees	tobiu
createdAt	Mar 8, 2026, 5:22 PM
updatedAt	Mar 8, 2026, 5:24 PM
githubUrl	https://github.com/neomjs/neo/issues/9393
author	tobiu
commentsCount	1
parentIssue	9380
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 8, 2026, 5:24 PM

E2E: Implement GridRowScrollPinning via CSS Variables

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

Closed v12.1.0 enhancementaiarchitecturegrid

tobiu commented on Mar 8, 2026, 5:22 PM

This ticket tracks the implementation of the CSS Variables strategy for Optical Row Pinning, designed to perfectly satisfy the two core goals:

Leave wheel based scrolling alone.
Ensure rows are visible on massive thumb drags (heal on scroll end).

The Implementation:

CSS Variables (Neo.grid.Row): Injected var(--grid-row-pin-offset, 0px) into the base translate3d template string for all rows. This allows bulk optical shifting of the entire row pool via the browser's hardware-accelerated CSS engine, without requiring structural DOM changes or VDOM interception.
Synchronous Engine (GridRowScrollPinning): The addon now listens to the native scroll event and synchronously calculates the deltaY against the worker's baseline.
Absolute Threshold: A high absolute threshold (e.g., 500px) is used to ensure the addon completely ignores normal wheel scrolling, allowing native physics to govern small movements perfectly. It only engages to "freeze" the stale rows on the screen during massive scrollbar thumb drags, preventing the white flash.
Healing: The VDOM onDeltaUpdate event synchronously clears the CSS variable (0px) when the worker finally catches up, snapping the fresh data into place.

tobiu added the enhancement label on Mar 8, 2026, 5:22 PM

tobiu added the ai label on Mar 8, 2026, 5:22 PM

tobiu added the architecture label on Mar 8, 2026, 5:22 PM

tobiu added the grid label on Mar 8, 2026, 5:22 PM

tobiu added parent issue #9380 on Mar 8, 2026, 5:23 PM

tobiu referenced in commit f23b49a - "Enhancement: Implement GridRowScrollPinning via CSS Variables (#9393) on Mar 8, 2026, 5:23 PM

tobiu assigned to @tobiu on Mar 8, 2026, 5:24 PM

tobiu Mar 8, 2026, 5:24 PM

Input from Gemini 3.1 Pro:

✦ The CSS Variables architecture with the absolute 500px threshold has been committed and pushed to the repository.

This marks a major pivot in the Epic strategy:

We acknowledge that perfect pixel-sync between native scroll and async workers is impossible without breaking UX or generating extreme jitter.

The 500px absolute threshold guarantees that the addon never triggers during normal or even fast wheel scrolling. Wheel physics remain 100% native and smooth.

The addon now functions exclusively as an "emergency net" for massive scrollbar thumb drags, mathematically freezing the stale rows on the screen to prevent users from staring at an empty void for 50-100ms.

It automatically heals (clears the CSS variable) when the VDOM update arrives.

Closing this sub-ticket to set our new baseline. We can now proceed to testing the DevIndex grid.

tobiu closed this issue on Mar 8, 2026, 5:24 PM