What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	9623
title	Grid Multi-Body: Fix .neo-last-column border styling logic across multiple bodies
state	Closed
labels	bugaigrid
assignees	tobiu
createdAt	Apr 1, 2026, 10:03 PM
updatedAt	Apr 1, 2026, 10:25 PM
githubUrl	https://github.com/neomjs/neo/issues/9623
author	tobiu
commentsCount	0
parentIssue	9486
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 1, 2026, 10:25 PM

Grid Multi-Body: Fix .neo-last-column border styling logic across multiple bodies

Closed v13.0.0/archive-v13-0-0-chunk-1 bugaigrid

tobiu commented on Apr 1, 2026, 10:03 PM

Problem

The .neo-last-column CSS class removes the right border of a grid column because the Grid Container itself provides the bounding border. In the single-body architecture, this was correctly applied to the single rightmost column.

With the introduction of the multi-body architecture, isLastColumn evaluates to true for the last column of each sub-grid body (bodyStart, body, and bodyEnd). As a result, all three bodies were rendering a .neo-last-column without a right border, causing missing vertical dividers between sections.

Solution

Updated the isLastColumn logic in src/grid/Row.mjs to evaluate the global grid layout rather than just the local sub-grid count:

locked: 'start': Only gets .neo-last-column if there are no center columns and no end columns.
center: Only gets .neo-last-column if there are no end columns.
locked: 'end': Always receives .neo-last-column (as it represents the absolute rightmost boundary).

tobiu added the bug label on Apr 1, 2026, 10:03 PM

tobiu added the ai label on Apr 1, 2026, 10:03 PM

tobiu added the grid label on Apr 1, 2026, 10:03 PM

tobiu added parent issue #9486 on Apr 1, 2026, 10:03 PM

tobiu referenced in commit d275916 - "fix: Fix .neo-last-column CSS logic across multiple sub-grids (#9623) on Apr 1, 2026, 10:05 PM

tobiu assigned to @tobiu on Apr 1, 2026, 10:25 PM

tobiu closed this issue on Apr 1, 2026, 10:25 PM