What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	9281
title	DomEvents: Prevent duplicate local DOM event listeners
state	Closed
labels	bugaicore
assignees	tobiu
createdAt	Feb 24, 2026, 2:44 AM
updatedAt	Feb 24, 2026, 2:45 AM
githubUrl	https://github.com/neomjs/neo/issues/9281
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Feb 24, 2026, 2:45 AM

DomEvents: Prevent duplicate local DOM event listeners

Closed v12.0.0/archive-v12-0-0-chunk-4 bugaicore

tobiu commented on Feb 24, 2026, 2:44 AM

When calling addDomListeners() on a component that is already mounted, the mountDomListeners routine would re-send all existing local events (like mousemove) to the Main thread, resulting in duplicate addEventListener bindings and doubled postMessage traffic.

Root Cause: mountDomListeners was iterating over all registered listeners for a component and adding them to the payload sent to the App Worker, without checking if they had already been mounted.

Resolution:

Updated mountDomListeners in src/manager/DomEvent.mjs to check !event.mounted for local events, and set event.mounted = true before sending.
Added resetMountedDomListeners() to DomEvent manager to reset the flag when a component unmounts.
Added resetMountedDomEvents() to src/mixin/DomEvents.mjs.
Called me.resetMountedDomEvents?.() in src/component/Abstract.mjs when afterSetMounted is false (unmounting). This ensures listeners are only sent once and correctly re-attached if the component remounts.

tobiu Feb 24, 2026, 2:45 AM

The fix has been implemented and pushed to the dev branch.