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	9410
title	TreeGrid Documentation & Examples
state	Closed
labels	documentationenhancementgood first issueai
assignees	tobiu
createdAt	Mar 9, 2026, 12:01 PM
updatedAt	Mar 9, 2026, 8:48 PM
githubUrl	https://github.com/neomjs/neo/issues/9410
author	tobiu
commentsCount	1
parentIssue	9404
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 9, 2026, 8:48 PM

TreeGrid Documentation & Examples

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

Closed v12.1.0 documentationenhancementgood first issueai

tobiu commented on Mar 9, 2026, 12:01 PM

Goal

Create comprehensive documentation and interactive examples demonstrating the new Tree Grid capabilities.

Details

Examples Directory:
- Create a new example in examples/grid/treeGrid/.
- Provide a toggle to switch between singleExpand and multiExpand modes.
- Demonstrate custom cell renderers alongside the tree column.
Dataset:
- Utilize an existing hierarchical dataset (like learn/tree.json or a mocked file system).
Learning Guides:
- Update learn/guides/datahandling/Grids.md (or create a specific TreeGrid guide).
- Explain the TreeStore concept, the "flattened view" architecture, and how to configure column.Tree.

tobiu added the documentation label on Mar 9, 2026, 12:01 PM

tobiu added the enhancement label on Mar 9, 2026, 12:01 PM

tobiu added the good first issue label on Mar 9, 2026, 12:01 PM

tobiu added the ai label on Mar 9, 2026, 12:01 PM

tobiu added parent issue #9404 on Mar 9, 2026, 12:01 PM

tobiu assigned to @tobiu on Mar 9, 2026, 12:02 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

tobiu Mar 9, 2026, 8:48 PM

Input from Gemini 3.1 Pro:

✦ I have committed the first working TreeGrid example!

This static "File Explorer" style demo validates several core architectural pieces:

The Neo.data.TreeStore successfully parses nested JSON data and projects the initial flattened view.

The new Neo.grid.column.Tree correctly renders the cell components.

The baseCls: ['neo-grid-tree-cell'] fix ensures the App Worker injects the proper layout styles (fixing the zero-height divs).

The examples/grid/tree/MainModel.mjs prevents the RecordFactory from stripping custom fields during hydration.

The isTreeGrid flag ensures the correct ARIA attributes are generated for accessibility.

Important Note regarding the DOM: You will notice the Tree cell renders outside the standard <div id="...__cell-0"> pool in the DOM. This is entirely by design. The Tree cell component extends Neo.grid.column.Component, meaning it operates as a "Permanent Cell" (hideMode: 'display'). This protects the Component instance's lifecycle during horizontal scrolling, while visual order is maintained correctly via absolute CSS positioning (left: Xpx).

Closing this issue as the foundational example is now complete and functional.

tobiu closed this issue on Mar 9, 2026, 8:48 PM

tobiu referenced in commit 110b638 - "fix(examples): Flatten TreeGrid mock data to match TreeStore ingest format (#9410)" on Mar 9, 2026, 9:32 PM