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	9407
title	Create `Neo.grid.column.Tree` & Cell Component
state	Closed
labels	enhancementdesignaigrid
assignees	tobiu
createdAt	Mar 9, 2026, 11:52 AM
updatedAt	Mar 9, 2026, 5:20 PM
githubUrl	https://github.com/neomjs/neo/issues/9407
author	tobiu
commentsCount	2
parentIssue	9404
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 9, 2026, 5:20 PM

Create `Neo.grid.column.Tree` & Cell Component

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

Closed v12.1.0 enhancementdesignaigrid

tobiu commented on Mar 9, 2026, 11:52 AM

Goal

Implement the specialized column renderer for Tree Grids, using a nested component architecture to handle indentation, toggle states, and event emission without breaking Row Pooling.

Details

src/grid/column/Tree.mjs:
- Extends Neo.grid.column.Component.
- Defaults to using Neo.grid.column.tree.Component.
- Implements expand(record) and collapse(record) proxy methods to forward the interaction to the TreeStore.
src/grid/column/tree/Component.mjs:
- Extends Neo.component.Base.
- VDOM Structure: Indentation Spacer (CSS variable bound), Toggle Icon (CSS class bound), and Content Node.
- Reacts to record changes (during scroll recycling) to update its internal depth, expanded, and isLeaf states.
SCSS Implementation (src + 5 themes):
- src/.../Component.scss: Structural flex layout and CSS calc() for indentation.
- theme-*/.../Component.scss: Define FontAwesome icons for expanded/collapsed states using ::before pseudo-elements.
Interaction & Events:
- Add click delegation on the toggle icon.
- The column must trigger the expansion/collapse via the TreeStore.
- Crucial: The TreeStore (or the column itself) must fire expand and collapse events.
- These events should bubble up to (or be explicitly fired on) the grid.Container so developers can easily listen to them in their View Controllers (e.g., onNodeExpand, onNodeCollapse).

tobiu added the enhancement label on Mar 9, 2026, 11:52 AM

tobiu added the design label on Mar 9, 2026, 11:52 AM

tobiu added the ai label on Mar 9, 2026, 11:52 AM

tobiu added the grid label on Mar 9, 2026, 11:52 AM

tobiu added parent issue #9404 on Mar 9, 2026, 11:52 AM

tobiu Mar 9, 2026, 12:09 PM

Input from Gemini 3.1 Pro:

✦ Implementation Guidance for Agents:

When implementing the styling for this component, you MUST adhere to the Neo.mjs split styling architecture:

Structural Layout (resources/scss/src/grid/column/tree/Component.scss):

This file should ONLY contain layout rules (Flexbox alignment, margins).

Use a CSS calc() with a variable for indentation: width: calc(var(--tree-depth, 0) * var(--tree-indent, 16px));

Theme Variables (resources/scss/theme-*/grid/column/tree/Component.scss):

You must create this file for ALL 5 themes (theme-neo-dark, theme-neo-light, theme-neo-light-rich, theme-neo-dark-rich, theme-epona).

Define the actual CSS variables (e.g., --tree-indent) here.

Define the visual icons using ::before pseudo-elements and the content property mapped to FontAwesome unicode values (e.g., content: '\f054' for collapsed, \f078 for expanded).

Important Files to Reference:

Look at src/grid/column/Component.mjs to understand how the cell recycling works via afterSetRecord.

Look at resources/scss/theme-neo-dark/grid/column/IconLink.scss for an example of how to scope theme-specific column styling.

tobiu assigned to @tobiu on Mar 9, 2026, 12:10 PM

tobiu referenced in commit 78767bb - "feat(grid): Create Neo.grid.column.Tree & Cell Component (#9407)" on Mar 9, 2026, 5:19 PM

tobiu Mar 9, 2026, 5:19 PM

Input from Gemini 3.1 Pro:

✦ I have implemented Neo.grid.column.Tree and Neo.grid.column.component.Tree. The cell component handles visual state updating (indents via depth_, CSS icons via isLeaf_ & expanded_). Click events on the toggle delegate back to the gridContainer, which subsequently triggers store.expand() and store.collapse(), as well as explicit expand/collapse events emitted on the grid itself.

I've also used NeoArray.remove(cls, ['is-expanded', 'is-collapsed', 'is-leaf']) as suggested! Closing this issue as complete.

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

tobiu referenced in commit 19771c9 - "fix(grid): Correct Tree theme folders and apply missing baseCls (#9407) on Mar 9, 2026, 8:48 PM

tobiu referenced in commit 524bb31 - "fix(grid): Correct themes, fix baseCls layout, and add TreeGrid demo (#9407) (#9410) on Mar 9, 2026, 8:48 PM

Create Neo.grid.column.Tree & Cell Component

Goal

Details

Create `Neo.grid.column.Tree` & Cell Component