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	9529
title	Add lightweight cell resizing method to grid.Body
state	Closed
labels	enhancementaigrid
assignees	tobiu
createdAt	Mar 20, 2026, 5:21 PM
updatedAt	Mar 20, 2026, 5:34 PM
githubUrl	https://github.com/neomjs/neo/issues/9529
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[x] 9528 Real-time cell resizing during grid column drag:move
closedAt	Mar 20, 2026, 5:34 PM

Add lightweight cell resizing method to grid.Body

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

Closed v12.1.0 enhancementaigrid

tobiu commented on Mar 20, 2026, 5:21 PM

Description

As a prerequisite for real-time grid cell resizing during a column drag (Issue #9528), we need a lightweight method in src/grid/Body.mjs to adjust cell widths and horizontal positions without causing a full row re-render.

Problem

Calling toolbar.passSizeToBody() on every drag:move tick triggers a full createViewData() cycle, destroying virtualization recycling benefits.

Solution

Implement updateCellPositions(dataField, newWidth) in src/grid/Body.mjs to:

Update the columnPositions collection cache.
Directly mutate the style.width of the resized column's cells in the VDOM.
Directly mutate the style.left of all subsequent columns' cells in the VDOM.
Update the scroll container's availableWidth.
Trigger a shallow VDOM update (updateDepth: 2) on the body to sync the DOM efficiently.

tobiu added the enhancement label on Mar 20, 2026, 5:21 PM

tobiu added the ai label on Mar 20, 2026, 5:21 PM

tobiu added the grid label on Mar 20, 2026, 5:21 PM

tobiu assigned to @tobiu on Mar 20, 2026, 5:22 PM

tobiu marked this issue as blocking #9528 on Mar 20, 2026, 5:23 PM

tobiu referenced in commit 5b58f5e - "feat: Add lightweight cell resizing method to grid.Body (#9529)" on Mar 20, 2026, 5:28 PM

tobiu Mar 20, 2026, 5:28 PM

Input from Gemini 3.1 Pro:

✦ I have implemented updateCellPositions inside src/grid/Body.mjs and hooked it into onDragMove in src/grid/header/plugin/Resizable.mjs using the shallow updateDepth: 2.

This directly adjusts the VDOM cell nodes without forcing full re-renders of the rows and avoiding toolbar.passSizeToBody() on every drag tick.

The changes have been pushed to the dev branch. Please review and verify the visual stability during a resize drag.

tobiu cross-referenced by #9528 on Mar 20, 2026, 5:33 PM

tobiu closed this issue on Mar 20, 2026, 5:34 PM