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	9054
title	Perf: Optimize GitHubOrgs with Node Pooling & Visibility
state	Closed
labels	bugaiperformance
assignees	tobiu
createdAt	Feb 8, 2026, 7:33 PM
updatedAt	Feb 8, 2026, 7:49 PM
githubUrl	https://github.com/neomjs/neo/issues/9054
author	tobiu
commentsCount	1
parentIssue	8930
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 8, 2026, 7:49 PM

Perf: Optimize GitHubOrgs with Node Pooling & Visibility

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

Closed v12.0.0 bugaiperformance

tobiu commented on Feb 8, 2026, 7:33 PM

The Neo.component.GitHubOrgs component contributes significantly to layout thrashing in the DevRank Grid. It currently rebuilds its VDOM children array on every data update, causing up to 5 removeNode and insertNode operations per cell during scrolling.

Optimization Strategy:

CSS Containment: Apply contain: layout paint style to .neo-github-orgs.
Node Pooling with Visibility: Refactor afterSetOrgs to maintain a fixed pool of maxItems (default 5) VDOM nodes.
- Initialize the pool once.
- Recycle nodes by updating attributes (src, href).
- Strict Stability: For unused nodes, set style: { visibility: 'hidden' } instead of display: none. This ensures the component dimensions remain absolutely constant, preventing any reflows in the parent grid cell.

Benefits:

Eliminates structural DOM changes (0 insert/remove ops).
Guarantees Zero Layout Shift (component size is immutable).
Isolates reflows to the component container.

tobiu added the bug label on Feb 8, 2026, 7:33 PM

tobiu added the ai label on Feb 8, 2026, 7:33 PM

tobiu added the performance label on Feb 8, 2026, 7:33 PM

tobiu referenced in commit 4fe7baf - "perf: Optimize GitHubOrgs with Node Pooling & Visibility (#9054)" on Feb 8, 2026, 7:39 PM

tobiu Feb 8, 2026, 7:39 PM

Input from Gemini 3 Pro:

✦ ✦ Optimization Implemented: Node Pooling with Visibility Toggling

To resolve the layout thrashing caused by the GitHubOrgs component during grid scrolling, we implemented a stable-DOM architecture.

1. CSS Containment & Visibility:

Applied contain: layout paint style; to the .neo-github-orgs wrapper.

Crucial Decision: We use visibility: hidden instead of display: none for unused slots. This ensures the component dimensions (width/height) remain absolutely constant regardless of the number of visible avatars. The component effectively reserves space for 5 avatars at all times, preventing any reflows in the parent grid cell.

2. Pre-allocated Node Pooling:

The component now initializes a fixed pool of maxItems (5) anchor/image nodes on the first data update.

Instead of destroying/recreating nodes, afterSetOrgs recycles them:

Used: Update attributes (src, href), set style: null (visible).

Unused: Clear attributes, set style: { visibility: 'hidden' }.

Impact:

Zero Structural Deltas: Scrolling generates 0 insertNode or removeNode operations for this column.

Zero Layout Shift: The component size is immutable, eliminating forced reflows.

60fps Scrolling: Verified that this change, combined with the CountryFlag optimization, restores smooth scrolling performance.

tobiu cross-referenced by #9055 on Feb 8, 2026, 7:49 PM

tobiu assigned to @tobiu on Feb 8, 2026, 7:49 PM

tobiu closed this issue on Feb 8, 2026, 7:49 PM

tobiu added parent issue #8930 on Feb 8, 2026, 7:49 PM