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	9055
title	Feat: Configurable renderFullPool for GitHubOrgs Component
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Feb 8, 2026, 7:49 PM
updatedAt	Feb 8, 2026, 7:54 PM
githubUrl	https://github.com/neomjs/neo/issues/9055
author	tobiu
commentsCount	1
parentIssue	8930
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 8, 2026, 7:54 PM

Feat: Configurable renderFullPool for GitHubOrgs Component

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

Closed v12.0.0 enhancementai

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

The optimization implemented in #9054 (Fixed Pool + Visibility Hidden) forces the GitHubOrgs component to always occupy the width of maxItems (5 avatars), even if empty. While this prevents reflows in Grids, it breaks standard layout expectations (shrink-to-fit) when the component is used in other contexts (e.g., Cards, Forms).

Tasks:

Configurable Strategy: Introduce a renderFullPool config to Neo.component.GitHubOrgs (default: false).
- false: Render only valid items (Standard Behavior).
- true: Render fixed pool with visibility: hidden (Grid Optimization).
Grid Integration: Update Neo.grid.column.GitHubOrgs to default this config to true.
Documentation: Apply the Knowledge Base Enhancement Strategy by adding rich JSDoc explaining the architectural trade-off.

tobiu added the enhancement label on Feb 8, 2026, 7:49 PM

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

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

tobiu referenced in commit b194f40 - "feat: Implement configurable renderFullPool for GitHubOrgs (#9055)" on Feb 8, 2026, 7:53 PM

tobiu Feb 8, 2026, 7:54 PM

Input from Gemini 3 Pro:

✦ Configurable Pooling Implemented

We have successfully decoupled the grid-specific optimization from the general component behavior.

Changes:

Neo.component.GitHubOrgs:

Added renderFullPool config (Default: false).

False (Standard): Renders only present items. Adapts to content.

True (Grid Optimized): Renders fixed pool of maxItems nodes using visibility: hidden for stability.

Added comprehensive JSDoc explaining the architectural trade-off.

Neo.grid.column.GitHubOrgs:

Updated default config to renderFullPool: true.

This ensures the Grid automatically opts-in to the zero-layout-shift behavior.

This solution preserves the performance gains for the DevRank Grid while keeping the GitHubOrgs component flexible for general use.

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

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