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	8990
title	perf: Propagate silent flag to Component Column renderer to suppress scrolling updates
state	Closed
labels	aiperformancecore
assignees	tobiu
createdAt	Feb 4, 2026, 8:41 PM
updatedAt	Feb 4, 2026, 8:47 PM
githubUrl	https://github.com/neomjs/neo/issues/8990
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 4, 2026, 8:47 PM

perf: Propagate silent flag to Component Column renderer to suppress scrolling updates

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

Closed v12.0.0 aiperformancecore

tobiu commented on Feb 4, 2026, 8:41 PM

Context

The grid scrolling performance has degraded after the Neo.grid.Row refactor. Analysis points to a message flood caused by Component Columns. When grid.Body scrolls, it updates rows silently (createViewData(silent=true)). However, Neo.grid.Row fails to propagate this silent flag to cellRenderer. Consequently, grid.column.Component calls component.set() without the silent flag, triggering an individual VDOM update for every component cell in every row on every scroll frame (e.g., 50 rows = 50 extra updates/frame).

Objective

Suppress individual component updates during the scrolling loop by propagating the silent flag.

Changes

src/grid/Row.mjs:
- Update createVdom to pass silent to applyRendererOutput.
- Update applyRendererOutput to accept silent and include it in the renderer data object.
src/grid/column/Component.mjs:
- Update cellRenderer to accept silent from data.
- Use component.set(config, silent) to leverage component.Abstract's silent update capability.

Expected Result

Significant reduction in VDOM traffic during scrolling for grids with component columns, restoring performance.

tobiu added the performance label on Feb 4, 2026, 8:41 PM

tobiu added the core label on Feb 4, 2026, 8:41 PM

tobiu added the ai label on Feb 4, 2026, 8:41 PM

tobiu assigned to @tobiu on Feb 4, 2026, 8:41 PM

tobiu referenced in commit 258be4e - "perf: Propagate silent flag to Component Column renderer to suppress scrolling updates (#8990)" on Feb 4, 2026, 8:46 PM

tobiu Feb 4, 2026, 8:47 PM

Input from Gemini 3 Pro:

✦ Implemented silent updates for Component Columns to fix scrolling performance regression.

Changes:

src/grid/Row.mjs:

Updated createVdom to pass the silent flag (received from Body.createViewData) to applyRendererOutput.

Updated applyRendererOutput to include silent in the data object passed to column.renderer.

src/grid/column/Component.mjs:

Updated cellRenderer to destructure silent from the data object.

Switched from component.set(config) to component.set(config, silent) to leverage the framework's native silent update capability.

This ensures that during scrolling, the 50+ recycled component instances update their internal state without triggering individual VDOM updates, relying instead on the single atomic VDOM update from the Grid Body.

tobiu closed this issue on Feb 4, 2026, 8:47 PM