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	9009
title	Extract GitHubUser and CountryFlag Grid Columns
state	Closed
labels	enhancementairefactoringcore
assignees	tobiu
createdAt	Feb 6, 2026, 1:45 AM
updatedAt	Feb 6, 2026, 2:13 AM
githubUrl	https://github.com/neomjs/neo/issues/9009
author	tobiu
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 6, 2026, 2:10 AM

Extract GitHubUser and CountryFlag Grid Columns

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

Closed v12.0.0 enhancementairefactoringcore

tobiu commented on Feb 6, 2026, 1:45 AM

Extract the UserCell and LocationCell components from the DevRank app into reusable Grid Columns in the framework core, as suggested.

Create Components:
- src/grid/column/GitHubUser.mjs (Column definition)
- src/component/GitHubUser.mjs (Cell component logic, moved from UserCell.mjs)
- src/grid/column/CountryFlag.mjs (Column definition)
- src/component/CountryFlag.mjs (Cell component logic, moved from LocationCell.mjs)
Move Styles:
- Extract SCSS from resources/scss/src/apps/devrank/GridContainer.scss.
- Create resources/scss/src/grid/column/GitHubUser.scss.
- Create resources/scss/src/grid/column/CountryFlag.scss.
Update DevRank:
- Refactor apps/devrank/view/GridContainer.mjs to use the new framework columns.
- Delete local UserCell.mjs and LocationCell.mjs.

tobiu added the enhancement label on Feb 6, 2026, 1:45 AM

tobiu added the ai label on Feb 6, 2026, 1:45 AM

tobiu added the refactoring label on Feb 6, 2026, 1:45 AM

tobiu added the core label on Feb 6, 2026, 1:45 AM

tobiu assigned to @tobiu on Feb 6, 2026, 2:09 AM

tobiu referenced in commit 0e66066 - "feat(core): Extract GitHubUser and CountryFlag columns (#9009)" on Feb 6, 2026, 2:09 AM

tobiu Feb 6, 2026, 2:09 AM

Input from Gemini 3 Pro:

✦ Extracted UserCell and LocationCell from DevRank into core framework components:

Neo.component.GitHubUser

Neo.component.CountryFlag

Registered corresponding Grid Columns in Neo.grid.Container.columnTypes:

githubUser -> Neo.grid.column.GitHubUser

countryFlag -> Neo.grid.column.CountryFlag

Refined implementation:

Components use baseCls for better extensibility.

SCSS files moved to resources/scss/src/component/ with alphabetically sorted properties.

DevRank GridContainer updated to use the new column types.

tobiu closed this issue on Feb 6, 2026, 2:10 AM

tobiu referenced in commit 71a1c71 - "cleanup(devrank): Remove obsolete cell components and styles (#9009)" on Feb 6, 2026, 2:12 AM

tobiu Feb 6, 2026, 2:13 AM

Input from Gemini 3 Pro:

✦ Pushed cleanup commit: Removed obsolete UserCell.mjs, LocationCell.mjs and cleaned up GridContainer.scss.