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	9510
title	Tooltip regression: dynamic domListeners bypassed reactivity and bubbling fixes
state	Closed
labels	bugaicore
assignees	tobiu
createdAt	Mar 18, 2026, 1:00 PM
updatedAt	Mar 18, 2026, 1:15 PM
githubUrl	https://github.com/neomjs/neo/issues/9510
author	tobiu
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 18, 2026, 1:15 PM

Tooltip regression: dynamic domListeners bypassed reactivity and bubbling fixes

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

Closed v12.1.0 bugaicore

tobiu commented on Mar 18, 2026, 1:00 PM

In Neo v12, dynamic DOM event registration (e.g., addDomListeners) failed due to three separate bugs in the event architecture:

Reactivity Bypass: src/mixin/DomEvents.mjs mutated the this.domListeners array in place. The core.Config system's isEqual check evaluated the identical array reference as unchanged, bypassing the afterSetDomListeners hook entirely. Fixed by spreading into a new array.
Bubbling Cancellation: In src/manager/DomEvent.mjs, the global bubble flag was cancelled if !listener.bubble was true. Since omitted configs are undefined, !undefined evaluated to true, incorrectly cancelling event bubbling for any listener that didn't explicitly set bubble: true. Fixed to explicitly check for listener.bubble === false.
Boolean Parsing in Manager: In DomEvent.updateDomListeners, resolving the bubble config used an || operator (domListener.bubble || value.bubble), losing explicitly set false values and failing to default to true. Fixed to use hasOwnProperty. Additionally, fixed a potential crash where vnodeId lacked a fallback to config.id if vdom was not present in the register method.

tobiu added the bug label on Mar 18, 2026, 1:00 PM

tobiu added the ai label on Mar 18, 2026, 1:00 PM

tobiu added the core label on Mar 18, 2026, 1:00 PM

tobiu referenced in commit 5348eb1 - "fix(core): Resolve dynamic domListeners reactivity bypass and bubble cancellation (#9510) on Mar 18, 2026, 1:00 PM

tobiu Mar 18, 2026, 1:01 PM

Input from Gemini 3.1 Pro:

✦ Completed the fix.

Commit: 5348eb155

Resolved the following issues:

Bubbling Cancellation: In src/manager/DomEvent.mjs, fixed the event loop check to explicitly use listener.bubble === false instead of !listener.bubble.

Boolean Parsing in Manager: Fixed DomEvent.updateDomListeners to use hasOwnProperty for bubble config parsing rather than ||.

vnodeId Consistent Fallback: Added fallback logic to config.id in manager/DomEvent.mjs register method to prevent crashes when a VDOM object isn't present yet.

tobiu referenced in commit f1b55cc - "refactor(core): Implement cloneOnGet for domListeners reactivity (#9510) on Mar 18, 2026, 1:14 PM

tobiu Mar 18, 2026, 1:14 PM

Input from Gemini 3.1 Pro:

✦ Added architectural refactoring.

Commit: f1b55cc7b

Reverted the manual [...this.domListeners] array spread hacks in favor of a cleaner configuration-level fix: we changed the domListeners_ config to use a descriptor with cloneOnGet: 'shallow'.

This ensures that any time a developer accesses this.domListeners, they receive a new array reference. If they mutate it (e.g. .push()) and assign it back, core.Config naturally detects the reference difference and triggers the afterSetDomListeners reactivity hook. This makes the system inherently more maintainable and resilient to accidental reactivity bypasses across the entire framework.

tobiu assigned to @tobiu on Mar 18, 2026, 1:15 PM

tobiu closed this issue on Mar 18, 2026, 1:15 PM