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	8985
title	refactor: Add getRow helper to GridBody
state	Closed
labels	airefactoring
assignees	tobiu
createdAt	Feb 4, 2026, 2:28 PM
updatedAt	Feb 4, 2026, 2:33 PM
githubUrl	https://github.com/neomjs/neo/issues/8985
author	tobiu
commentsCount	1
parentIssue	8964
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 4, 2026, 2:33 PM

refactor: Add getRow helper to GridBody

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

Closed v12.0.0 airefactoring

tobiu commented on Feb 4, 2026, 2:28 PM

Objective: Refactor the logic for retrieving a Neo.grid.Row component instance given a data record into a reusable helper method getRow(record) within Neo.grid.Body.

Current State: Neo.grid.column.AnimatedChange manually calculates the row index and accesses the body's item array using modulo arithmetic:

row = body.items[body.store.indexOf(record) % body.items.length]

Proposed Change:

Implement Neo.grid.Body.getRow(record):
- Find the record's index in the store.
- Verify the index is within the currently mountedRows range.
- Return the corresponding Row component from the pool.
Update Consumers: Refactor Neo.grid.column.AnimatedChange to use this new method.

Benefits:

Encapsulation: Hides row pooling implementation details (modulo logic) from columns.
Safety: Ensures the returned row is actually currently mounted and assigned to the target record.
Reusability: Useful for other column types or controllers needing row access.

tobiu added the ai label on Feb 4, 2026, 2:28 PM

tobiu added the refactoring label on Feb 4, 2026, 2:28 PM

tobiu referenced in commit 04c2bc6 - "refactor: Add getRow helper to GridBody (#8985)" on Feb 4, 2026, 2:31 PM

tobiu Feb 4, 2026, 2:32 PM

Input from Gemini 3 Pro:

✦ I have implemented the getRow helper and refactored AnimatedChange to use it.

Changes:

src/grid/Body.mjs: Added getRow(record). This method encapsulates the logic for finding a row component:

It retrieves the record index.

It checks if the index is within the mountedRows range (safety check).

It returns the recycled row component using modulo arithmetic on the pool size.

src/grid/column/AnimatedChange.mjs: Updated to use body.getRow(record) instead of manual calculation. This is cleaner and safer.

I have pushed the changes to the feature branch.

tobiu assigned to @tobiu on Feb 4, 2026, 2:33 PM

tobiu added parent issue #8964 on Feb 4, 2026, 2:33 PM

tobiu closed this issue on Feb 4, 2026, 2:33 PM