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	9485
title	Grid: Horizontal Scroll Performance & Jitter for Locked Columns
state	Closed
labels	bugaigrid
assignees	tobiu
createdAt	Mar 16, 2026, 4:08 PM
updatedAt	Mar 16, 2026, 8:37 PM
githubUrl	https://github.com/neomjs/neo/issues/9485
author	tobiu
commentsCount	0
parentIssue	9456
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 16, 2026, 8:37 PM

Grid: Horizontal Scroll Performance & Jitter for Locked Columns

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

Closed v12.1.0 bugaigrid

tobiu commented on Mar 16, 2026, 4:08 PM

We implemented the core architectural requirements for the locked columns feature, but horizontal scrolling performance is currently laggy and jitterish. The locked columns visually lag behind while scrolling, taking hundreds of milliseconds to catch up.

We have applied some initial fixes (throttling the main thread addon, implementing cell recycling for Pass 2 to reduce VDOM deltas, and resolving an issue with the visibility state of locked Component columns), but further investigation is needed to achieve 60fps locked column pinning.

We need to deeply profile the horizontal scroll event pipeline and challenge the CSS architecture (e.g. relying on both left for layout and transform: translateX for offsets).

Tasks:

Fix VDOM thrashing for locked cells by applying Pass 1 recycling logic to Pass 2.
Fix visibility bug causing locked Component columns (hideMode: 'visibility') to vanish.
Add requestAnimationFrame throttle to GridColumnScrollPinning.mjs to prevent CSS var flood.
Profile horizontal scroll tick performance.
Evaluate replacing left + transform with purely CSS variable-driven layout logic (left: calc(...)) or similar GPU-friendly approaches.

tobiu added the bug label on Mar 16, 2026, 4:08 PM

tobiu added the ai label on Mar 16, 2026, 4:08 PM

tobiu added the grid label on Mar 16, 2026, 4:08 PM

tobiu added parent issue #9456 on Mar 16, 2026, 4:09 PM

tobiu referenced in commit 269e4c8 - "fix: Resolve locked column VDOM thrashing and throttle pinning addon (#9485)" on Mar 16, 2026, 4:09 PM

tobiu assigned to @tobiu on Mar 16, 2026, 4:09 PM

tobiu closed this issue on Mar 16, 2026, 8:37 PM