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	8942
title	Refactor: DevRank Grid Location Column (VDOM + SCSS)
state	Closed
labels	airefactoring
assignees	tobiu
createdAt	Feb 1, 2026, 6:58 PM
updatedAt	Feb 2, 2026, 12:55 AM
githubUrl	https://github.com/neomjs/neo/issues/8942
author	tobiu
commentsCount	2
parentIssue	8930
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 1, 2026, 7:21 PM

Refactor: DevRank Grid Location Column (VDOM + SCSS)

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

Closed v12.0.0 airefactoring

tobiu commented on Feb 1, 2026, 6:58 PM

The 'Location' column in the DevRank grid suffers from layout issues when the text is too long, causing the row height to expand.

Requirements:

Refactor Renderer: Switch the 'Location' column renderer from returning an HTML string to returning a VDOM object.
CSS Truncation: Implement text truncation (text-overflow: ellipsis, white-space: nowrap) to handle long location names gracefully without breaking the row height.
SCSS Extraction: Move all inline styles for this column into the SCSS file (apps/devrank/resources/scss/view/GridContainer.scss or similar).

Acceptance Criteria:

Long location names are truncated with an ellipsis.
Grid row heights remain consistent.
No inline styles in the VDOM renderer.

tobiu added the ai label on Feb 1, 2026, 6:58 PM

tobiu added the refactoring label on Feb 1, 2026, 6:58 PM

tobiu added parent issue #8930 on Feb 1, 2026, 6:59 PM

tobiu referenced in commit 62511c5 - "refactor: DevRank Grid VDOM Renderers & SCSS (#8942)" on Feb 1, 2026, 7:14 PM

tobiu Feb 1, 2026, 7:15 PM

Input from Gemini 3 Pro:

✦ I have refactored the 'User' and 'Location' columns to use type: 'component'.

Changes:

Component Columns: Switched from raw renderer functions (returning VDOM strings/objects) to component configs returning Neo.component.Base configurations. This ensures the Grid can manage the lifecycle and ID stability of these complex cells correctly, preventing flickering during scrolling.

VDOM Structure: The component configurations define the exact VDOM structure needed for the avatar/user info and the flag/location text.

SCSS Updates: Extracted styles to GridContainer.scss and added classes (.user-cell, .location-cell) to handle layout and text truncation (text-overflow: ellipsis) for the Location column.

Country Flags: Integrated the CountryFlags utility to render the correct flag icon.

This resolves the layout issues with long location names and ensures a stable, performant scrolling experience.

tobiu referenced in commit 94775f3 - "refactor: DevRank Grid VDOM Renderers & SCSS (#8942)" on Feb 1, 2026, 7:16 PM

tobiu Feb 1, 2026, 7:18 PM

Input from Gemini 3 Pro:

✦ I have also hardened the CountryFlags.getFlagUrl() method to strictly validate that the resolved country code is a 2-letter lowercase string (a-z). This prevents the generation of invalid URLs when the location field contains non-standard characters (like '☁︎') that might have slipped through the normalization logic.

tobiu closed this issue on Feb 1, 2026, 7:21 PM

tobiu assigned to @tobiu on Feb 2, 2026, 12:55 AM