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	9527
title	Grid cells do not shrink on column resize drop due to minWidth constraint
state	Closed
labels	bugaigrid
assignees	tobiu
createdAt	Mar 20, 2026, 2:14 PM
updatedAt	Mar 20, 2026, 2:16 PM
githubUrl	https://github.com/neomjs/neo/issues/9527
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 20, 2026, 2:16 PM

Grid cells do not shrink on column resize drop due to minWidth constraint

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

Closed v12.1.0 bugaigrid

tobiu commented on Mar 20, 2026, 2:14 PM

Description

When making a grid column narrower using the resizable handles, the header button shrinks correctly, but the grid cells below do not shrink.

This occurs because grid.Row initializes cells with minWidth: ${column.width}px. When grid.header.Toolbar#passSizeToBody updates the cell's width to a smaller value on drop, the existing min-width prevents the cell from physically shrinking.

Goal

Update grid.Row to apply width instead of minWidth, or ensure passSizeToBody also dynamically updates/clears minWidth when syncing column sizes.

tobiu added the bug label on Mar 20, 2026, 2:14 PM

tobiu added the ai label on Mar 20, 2026, 2:14 PM

tobiu added the grid label on Mar 20, 2026, 2:14 PM

tobiu assigned to @tobiu on Mar 20, 2026, 2:15 PM

tobiu referenced in commit 829c103 - "fix(grid): use width instead of minWidth for cell sizing (#9527) on Mar 20, 2026, 2:16 PM

tobiu Mar 20, 2026, 2:16 PM

Input from Gemini 3.1 Pro:

✦ Fixed in commit 829c10317. Replaced minWidth with width inside src/grid/Row.mjs cell creation logic. Grid cells now shrink appropriately when column resize drops happen.

tobiu closed this issue on Mar 20, 2026, 2:16 PM