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	9511
title	[Epic] Grid Value Banding
state	Closed
labels	enhancementepicaigrid
assignees	tobiu
createdAt	Mar 18, 2026, 3:15 PM
updatedAt	Mar 18, 2026, 3:18 PM
githubUrl	https://github.com/neomjs/neo/issues/9511
author	tobiu
commentsCount	2
parentIssue	null
subIssues	9512 Dynamic Value Banding Updates 9513 Optimize Grid Value Banding (startIndex Support) 9514 [Epic Sub] TreeStore Value Banding Support 9515 [Epic Sub] Value Banding styling conflicts with row selection
subIssuesCompleted	4
subIssuesTotal	4
blockedBy	[]
blocking	[]
closedAt	Mar 18, 2026, 3:18 PM

[Epic] Grid Value Banding

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

Closed v12.1.0 enhancementepicaigrid

tobiu commented on Mar 18, 2026, 3:15 PM

Implement a "value banding" effect for grid columns. This gives cells in a specific column with the same contiguous value the same background color. It requires updating the collection, store, grid container, and grid columns to propagate and compute this state.

Key architecture:

collection.Base maintains a valueBandsMap Map instance (keyed by recordId) to prevent V8 hidden class de-optimizations on the Record instances or raw data objects.
grid.Row queries store.valueBandsMap during applyRendererOutput to inject neo-value-band-1 or neo-value-band-2 CSS classes.
grid.Container supports body: { stripedRows: false } to disable alternating row colors which clash with value banding.
An example app is added to examples/grid/valueBanding.
Proper test suites are implemented in test/playwright/unit/collection/ValueBanding.spec.mjs and test/playwright/unit/data/StoreValueBandingCount.spec.mjs to ensure the recalculation algorithm only evaluates linearly on fields and efficiently updates state.

Sub-tasks:

Add valueBandingFields and calcValueBands to collection.Base
Update grid/Container and grid/Row to render the correct CSS classes (neo-value-band-1, neo-value-band-2)
Create SCSS variables for themes
Add stripedRows config to grid.Body
Add unit test for collection and store value banding
Create an example app examples/grid/valueBanding

tobiu added the enhancement label on Mar 18, 2026, 3:15 PM

tobiu added the epic label on Mar 18, 2026, 3:15 PM

tobiu added the ai label on Mar 18, 2026, 3:15 PM

tobiu added the grid label on Mar 18, 2026, 3:15 PM

tobiu referenced in commit f038194 - "feat(grid): Implement value banding for grid columns (#9511)" on Mar 18, 2026, 3:17 PM

tobiu assigned to @tobiu on Mar 18, 2026, 3:17 PM

tobiu Mar 18, 2026, 3:18 PM

Implemented via f0381948e

tobiu closed this issue on Mar 18, 2026, 3:18 PM

tobiu Mar 18, 2026, 3:18 PM

tobiu cross-referenced by #9512 on Mar 18, 2026, 3:43 PM

tobiu added sub-issue #9512 on Mar 18, 2026, 3:45 PM

tobiu cross-referenced by #9513 on Mar 18, 2026, 4:03 PM

tobiu added sub-issue #9513 on Mar 18, 2026, 4:04 PM

tobiu cross-referenced by #9514 on Mar 18, 2026, 4:07 PM

tobiu added sub-issue #9514 on Mar 18, 2026, 4:08 PM

tobiu cross-referenced by #9515 on Mar 18, 2026, 7:21 PM

tobiu added sub-issue #9515 on Mar 18, 2026, 7:21 PM