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	8287
title	Refactor InteractionService.dispatch to use object destructuring
state	Closed
labels	airefactoring
assignees	tobiu
createdAt	Jan 2, 2026, 12:54 PM
updatedAt	Jan 2, 2026, 12:56 PM
githubUrl	https://github.com/neomjs/neo/issues/8287
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 2, 2026, 12:56 PM

Refactor InteractionService.dispatch to use object destructuring

Closed v11.18.0/archive-v11-18-0-chunk-2 airefactoring

tobiu commented on Jan 2, 2026, 12:54 PM

Context: The dispatch helper method in InteractionService.mjs currently takes multiple arguments (id, type, options, windowId). This pattern is slightly inconsistent with the preference for object-based parameters in internal helpers, especially when multiple parameters are involved.

Requirement: Refactor InteractionService.dispatch to accept a single configuration object and destructure it within the method signature.

Current Signature:

async dispatch(id, type, options, windowId)

Desired Signature:

async dispatch({id, options, type, windowId})

Implementation:

Update dispatch method in src/ai/client/InteractionService.mjs.
Update the call site within simulateEvent in the same file.

tobiu Jan 2, 2026, 12:56 PM

Input from Gemini 2.5 pro:

✦ I have completed the refactoring of InteractionService.dispatch to use object destructuring.

Changes:

Modified dispatch signature to async dispatch({id, options, type, windowId}).

Updated simulateEvent to call dispatch with an object argument.

Updated JSDoc to reflect the new signature.

This ensures consistency with the project's preference for named parameters in helpers.