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	9607
title	GridContainer: `this.items is not iterable` crash on initialization
state	Closed
labels	bugaigrid
assignees	tobiu
createdAt	Mar 31, 2026, 12:33 PM
updatedAt	Mar 31, 2026, 12:34 PM
githubUrl	https://github.com/neomjs/neo/issues/9607
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 31, 2026, 12:34 PM

GridContainer: `this.items is not iterable` crash on initialization

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

Closedbugaigrid

tobiu commented on Mar 31, 2026, 12:33 PM

The recent layout engine refactoring in #9487 introduced headerWrapper and bodyWrapper containers into GridContainer. However, nested instances (headerToolbar and body) retained parentId: me.id injections from their beforeSet... pipelines. Consequently, the internal Container.createItem engine misidentified their explicit wrapper containers, triggering a premature deep DOM parent.remove() method against the still-initializing GridContainer. This caused a fatal this.items is not iterable exception as GridContainer.items defaults to null before finalization.

Fix Details: Removed the explicit parentId: me.id initialization inside beforeSetBody and beforeSetHeaderToolbar, correctly delegating contextual parentage mapping to the structural DOM composition layer (wrapper insertion).

tobiu added the bug label on Mar 31, 2026, 12:33 PM

tobiu added the ai label on Mar 31, 2026, 12:33 PM

tobiu added the grid label on Mar 31, 2026, 12:33 PM

tobiu referenced in commit 545efc2 - "fix: Resolve container items collision during sub-grid wrapper instantiation (#9607)" on Mar 31, 2026, 12:34 PM

tobiu Mar 31, 2026, 12:34 PM

Input from Gemini 3.1 Pro (Antigravity):

✦ Pushed the fix to completely remove the isolated parentId property conflict during instantiation boundaries.

Verification:
Both stacktrace errors are eradicated:

remove crash stemming from GridContainer.items defaults

removeDom misread originating from Viewport resolving an uninstantiated config object due to #1.

tobiu assigned to @tobiu on Mar 31, 2026, 12:34 PM

tobiu closed this issue on Mar 31, 2026, 12:34 PM

GridContainer: this.items is not iterable crash on initialization

GridContainer: `this.items is not iterable` crash on initialization