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	8464
title	Fix Blog List Rendering Artifact in Release View
state	Closed
labels	bug
assignees	tobiu
createdAt	Jan 9, 2026, 1:42 PM
updatedAt	Jan 9, 2026, 2:50 PM
githubUrl	https://github.com/neomjs/neo/issues/8464
author	tobiu
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 9, 2026, 2:13 PM

Fix Blog List Rendering Artifact in Release View

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

Closed v11.19.1 bug

tobiu commented on Jan 9, 2026, 1:42 PM

A rendering artifact has been observed in the Portal App where the Blog (News) List occasionally renders inside the Release Notes view, specifically taking over the Splitter component's DOM node.

Symptoms:

The Splitter in Portal.view.news.release.MainContainer (neo-splitter-1) acquires the class names of the Blog List Wrapper (portal-blog-list-wrapper).
The Splitter contains the Blog List (neo-list-2) as a child node in the VDOM/VNode tree.
This occurs during navigation between the News (Blog) and Release Notes tabs.

Theory (Potential Race Condition): This may be caused by a race condition rather than a direct VDOM diffing error.

The News (Blog) List initiates a large content update or roundtrip.
The user switches the tab to Release Notes before the update completes.
The pending update arrives and targets the same parent index (Item 1), which is now occupied by the Splitter in the new view.
The VDOM engine applies the update to the current occupant of that index, resulting in the "zombie" node state.

Fix: We will enforce VDOM node distinction by adding unique key properties to:

The Splitter in apps/portal/view/shared/content/Container.mjs.
The List in apps/portal/view/news/blog/Container.mjs.

This will force the VDOM engine to treat these as distinct nodes, tearing down the old one and creating the new one, regardless of timing or index collisions.

tobiu added the bug label on Jan 9, 2026, 1:42 PM

tobiu referenced in commit c454339 - "fix: Blog List Rendering Artifact in Release View (#8464)" on Jan 9, 2026, 2:12 PM

tobiu assigned to @tobiu on Jan 9, 2026, 2:12 PM

tobiu Jan 9, 2026, 2:12 PM

Input from Gemini 3 Pro:

✦ I have implemented the fix by enforcing unique, deterministic VDOM IDs for the conflicting components (Splitter and Blog List). This ensures the VDOM engine treats them as distinct nodes during view switching, preventing the race condition where one view's update "zombies" into the other.

Implementation Detail: Used onConstructed to dynamically set IDs based on the parent container's ID (${me.id}__splitter / ${me.id}__list). This avoids modifying the class construct logic and preserves extensibility.

Note: While this fixes the immediate artifact, the fact that manual IDs were required suggests a deeper issue in how the VDOM engine handles auto-generated ID syncing during rapid state transitions (race conditions). This should be investigated further in a separate initiative.

Commit: c4543396d (#8464)

tobiu closed this issue on Jan 9, 2026, 2:13 PM

tobiu cross-referenced by #8465 on Jan 9, 2026, 2:32 PM

tobiu Jan 9, 2026, 2:50 PM

Input from Gemini 3 Pro:

✦ ✦ Follow-up: The permanent architectural fix for this issue has been implemented and verified in #8465. The manual ID assignments previously added to the Portal app have been removed as they are no longer necessary.