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	9001
title	Update Grid Row Cell Border Logic for Pooling
state	Closed
labels	bugairegression
assignees	tobiu
createdAt	Feb 5, 2026, 12:04 PM
updatedAt	Feb 5, 2026, 12:10 PM
githubUrl	https://github.com/neomjs/neo/issues/9001
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 5, 2026, 12:10 PM

Update Grid Row Cell Border Logic for Pooling

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

Closed v12.0.0 bugairegression

tobiu commented on Feb 5, 2026, 12:04 PM

With the introduction of Hybrid Cell Pooling (#8992), the DOM order of cells (Pooled vs Permanent) no longer guarantees alignment with their visual order (column index). Consequently, the CSS rule &:last-child on .neo-grid-cell incorrectly targets the last rendered DOM node (which might be a pooled cell in the middle of the grid, or a permanent cell rendered last) instead of the visually last column. This results in incorrect right-borders.

Solution:

Update Neo.grid.Row to calculate which column is the last visible column and apply a specific CSS class (e.g., neo-last-column) to its corresponding cell.
Update resources/scss/src/grid/Body.scss to use .neo-last-column instead of &:last-child for removing the right border.

Note: This logic must account for both pooled and permanent cells.

tobiu added the bug label on Feb 5, 2026, 12:04 PM

tobiu added the ai label on Feb 5, 2026, 12:04 PM

tobiu added the regression label on Feb 5, 2026, 12:04 PM

tobiu assigned to @tobiu on Feb 5, 2026, 12:05 PM

tobiu referenced in commit fe851d4 - "fix: Update Grid Row Cell Border Logic for Pooling (#9001)" on Feb 5, 2026, 12:09 PM

tobiu Feb 5, 2026, 12:09 PM

Input from Gemini 3 Pro:

✦ I have implemented the fix for the grid row cell border logic.

Changes:

Updated Neo.grid.Row#createVdom: Now calculates lastColumnIndex and passes an isLastColumn flag to applyRendererOutput.

Updated Neo.grid.Row#applyRendererOutput: Adds the neo-last-column CSS class to the cell configuration if isLastColumn is true. Updated JSDoc to match signature.

Updated resources/scss/src/grid/Body.scss: Replaced the :last-child selector with .neo-last-column for removing the right border.

This ensures the rightmost column visually (the one with the highest index) correctly has its border removed, regardless of the rendering order of pooled vs. permanent cells.

tobiu closed this issue on Feb 5, 2026, 12:10 PM