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	9278
title	Fix Grid Row Bottom Border and Remove Empty Scroll Row
state	Closed
labels	bugaigrid
assignees	tobiu
createdAt	Feb 24, 2026, 1:10 AM
updatedAt	Feb 24, 2026, 1:16 AM
githubUrl	https://github.com/neomjs/neo/issues/9278
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 24, 2026, 1:16 AM

Fix Grid Row Bottom Border and Remove Empty Scroll Row

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

Closed v12.0.0 bugaigrid

tobiu commented on Feb 24, 2026, 1:10 AM

Description The row pooling architecture means the last physical DOM row (:last-child) no longer consistently matches the last logical row of the dataset. Therefore, the CSS rule hiding the bottom border for the :last-child row causes missing borders on data rows.

Additionally, the grid scroll height calculation currently includes a + 1 row offset, resulting in an empty row at the bottom of the grid. Since removing the :last-child CSS fix ensures the final data row will always render its own bottom border, this extra scroll space is unnecessary and creates dead space.

Proposed Changes

Remove the :last-child border removal rule in resources/scss/src/grid/Body.scss.
Remove the + 1 extra row calculation in src/grid/Body.mjs and src/grid/VerticalScrollbar.mjs (updateScrollHeight).

tobiu added the bug label on Feb 24, 2026, 1:10 AM

tobiu added the ai label on Feb 24, 2026, 1:10 AM

tobiu added the grid label on Feb 24, 2026, 1:10 AM

tobiu referenced in commit 6338db0 - "fix(grid): remove :last-child border-bottom fix due to row pooling (#9278)" on Feb 24, 2026, 1:16 AM

tobiu assigned to @tobiu on Feb 24, 2026, 1:16 AM

tobiu Feb 24, 2026, 1:16 AM

Input from Gemini 3.1 Pro:

✦ I have removed the faulty :last-child CSS rule in Body.scss to restore the bottom border on data rows.

We discussed removing the + 1 empty row offset, but decided to keep it as it prevents the final data row from colliding visually with the bottom container boundary. Keeping it also avoids having to introduce additional evaluation logic into Row.mjs simply to strip the bottom border off the very last data row.

The changes have been pushed to the dev branch.

tobiu closed this issue on Feb 24, 2026, 1:16 AM