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	8703
title	fix: Wire up mouse events for Portal Services Canvas
state	Closed
labels	bugai
assignees	tobiu
createdAt	Jan 16, 2026, 1:50 PM
updatedAt	Jan 16, 2026, 2:01 PM
githubUrl	https://github.com/neomjs/neo/issues/8703
author	tobiu
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 16, 2026, 1:57 PM

fix: Wire up mouse events for Portal Services Canvas

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

Closed v11.23.0 bugai

tobiu commented on Jan 16, 2026, 1:50 PM

The Portal.view.services.Canvas component has methods for mousemove and mouseleave but is missing the domListeners configuration to actually trigger them. This prevents the interactive effects of the 'Architect's Grid' from working.

I will add the missing domListeners config:

domListeners: {
    mouseleave: 'onMouseLeave',
    mousemove : {fn: 'onMouseMove', local: true}
}

tobiu added the bug label on Jan 16, 2026, 1:50 PM

tobiu added the ai label on Jan 16, 2026, 1:50 PM

tobiu referenced in commit 1a58862 - "fix: Update Services View import path in Portal Viewport (#8703)" on Jan 16, 2026, 1:57 PM

tobiu Jan 16, 2026, 1:57 PM

Input from Gemini 3 Pro:

✦ Updated apps/portal/view/Viewport.mjs to import the renamed services/Container.mjs instead of the old Component.mjs. This fixes the runtime loading error for the Services view.

tobiu assigned to @tobiu on Jan 16, 2026, 1:57 PM

tobiu closed this issue on Jan 16, 2026, 1:57 PM

tobiu referenced in commit 5faa5df - "chore: Finalize file renames for Services Container (#8703)" on Jan 16, 2026, 1:59 PM

tobiu Jan 16, 2026, 2:01 PM

Input from Gemini 3 Pro:

✦ Final Commit: Executed git add -A to correctly stage the file renames (Component -> Container) which were missed in the previous commit. This ensures the repository is in a clean state and the old files are properly deleted.

Summary of Resolution:

Refactoring: Renamed Portal.view.services.Component to Portal.view.services.Container to align with the framework architecture. Updated SCSS file names accordingly.

Event Handling: Moved mouse listeners to the container and implemented explicit forwarding to the ServicesCanvas instance, resolving the z-index interaction blocking issue.

Visualization: Implemented the "Architect's Grid" SharedWorker canvas with glassmorphism UI.

Consistency: Aligned hover effects and visual styling with the Portal Home section.