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	9288
title	[Enhancement] Generic Theme Support for Icon and IconLink Grid Columns
state	Closed
labels	enhancementgrid
assignees	tobiu
createdAt	Feb 24, 2026, 11:48 AM
updatedAt	Feb 24, 2026, 11:54 AM
githubUrl	https://github.com/neomjs/neo/issues/9288
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 24, 2026, 11:54 AM

[Enhancement] Generic Theme Support for Icon and IconLink Grid Columns

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

Closed v12.0.0 enhancementgrid

tobiu commented on Feb 24, 2026, 11:48 AM

Context Currently, Neo.grid.column.Icon and Neo.grid.column.IconLink render their inner components using the default inherit font-size from Neo.component.Icon. When placed inside a grid (where the default text size is 13px), these icons often appear too small (e.g., social media icons or status badges).

The Problem If an application wants to increase the size of these icons to 16px to make them legible within a grid, developers are forced to write custom, app-specific CSS overrides that target the .neo-grid-cell and the specific column classes (e.g., .devindex-column-linkedin). This pollutes app-level SCSS and prevents a consistent, out-of-the-box experience.

The Solution Leverage the architectural pattern where non-component grid columns (extending core.Base) can still inject theme files via afterSetWindowId().

We will create generic SCSS files for these columns:

resources/scss/src/grid/column/Icon.scss
resources/scss/src/grid/column/IconLink.scss
And corresponding variable definitions for theme-neo-dark and theme-neo-light.

These files will define CSS variables like --grid-column-icon-font-size: 16px specifically scoped within .neo-grid-cell, ensuring consistent 16px icons and properly aligned 13px labels for all Icon/IconLink columns across the framework, without affecting standalone components.

tobiu added the enhancement label on Feb 24, 2026, 11:48 AM

tobiu added the grid label on Feb 24, 2026, 11:48 AM

tobiu assigned to @tobiu on Feb 24, 2026, 11:50 AM

tobiu Feb 24, 2026, 11:50 AM

Input from Gemini 3.1 Pro:

✦ I have implemented the generic SCSS files and the Base.mjs documentation.

Six new SCSS files were created across src, theme-neo-dark, and theme-neo-light to establish a generic 16px baseline for Icon and IconLink columns when rendered inside .neo-grid-cell.

I also added an intent-driven JSDoc comment to src/grid/column/Base.mjs documenting the "Non-Component Theme Injection" architectural pattern to ensure developers understand how and why this works.

The changes are staged and ready for commit.

tobiu referenced in commit 3d04f29 - "feat(grid): Implement generic theme support for Icon and IconLink columns (#9288)" on Feb 24, 2026, 11:51 AM

tobiu closed this issue on Feb 24, 2026, 11:54 AM