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	9155
title	[DevIndex] Grid Icon Columns fail to update on Filter change
state	Closed
labels	bugai
assignees	tobiu
createdAt	Feb 14, 2026, 7:46 PM
updatedAt	Feb 14, 2026, 8:15 PM
githubUrl	https://github.com/neomjs/neo/issues/9155
author	tobiu
commentsCount	1
parentIssue	9106
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 14, 2026, 8:15 PM

[DevIndex] Grid Icon Columns fail to update on Filter change

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

Closed v12.0.0 bugai

tobiu commented on Feb 14, 2026, 7:46 PM

Icon and IconLink components (and potentially others) using hideMode: 'visibility' fail to reappear after being hidden.

Diagnosis: The show() method in src/component/Base.mjs attempts to restore visibility by deleting the visibility property from the style object:

let style = me.style;
delete style.visibility;
me.style = style;

However, debug logs confirm that vdom.style retains {visibility: 'hidden'} even after me.style becomes {}. This suggests that vdom.style (or wrapperStyle) might be retaining the property, or the spread merge {...me.wrapperStyle, ...me.style} in updateStyle is not clearing it as expected.

Solution: Override afterSetHidden in Icon.mjs and IconLink.mjs to explicitly set visibility: 'visible' (or null) instead of relying on property deletion. This forces a value change that propagates to the VDOM delta.

Long-term: Investigate if Component.mjs show() needs a generic fix (e.g. setting null instead of delete).

tobiu added the bug label on Feb 14, 2026, 7:46 PM

tobiu added the ai label on Feb 14, 2026, 7:46 PM

tobiu added parent issue #9106 on Feb 14, 2026, 7:46 PM

tobiu assigned to @tobiu on Feb 14, 2026, 7:46 PM

tobiu referenced in commit 3390cae - "fix(core): Resolve Icon visibility update failure on Grid filtering (#9155) on Feb 14, 2026, 8:14 PM

tobiu Feb 14, 2026, 8:15 PM

Input from Gemini 3 Pro:

✦ Fixed the Icon visibility update regression.

Root Cause: Component.updateStyle merges wrapperStyle and style. Since wrapperStyle reads the current vdom.style as a default (to support runtime hacks), styles persist in wrapperStyle once merged. Base.show() attempted to clear visibility by deleting the property from the style config. This removed the override but exposed the underlying "polluted" state in wrapperStyle (which still had visibility: hidden), causing the show operation to fail visually.

Fix: Updated Base.show() to explicitly set style.visibility = null. This forces a value change that overrides the polluted wrapperStyle, triggers the correct VDOM delta, and clears the persistence loop on the next cycle.

Documentation: Added JSDoc warnings to style_ and wrapperStyle_ in Base.mjs regarding this persistent state behavior and the need for explicit nulling.

tobiu closed this issue on Feb 14, 2026, 8:15 PM

tobiu referenced in commit 1968417 - "docs(core): Enhance Component style config documentation (#9155) on Feb 14, 2026, 8:19 PM