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	9313
title	Header Canvas: Fix layout syncing on mobile and dynamic item sizing
state	Closed
labels	bugai
assignees	tobiu
createdAt	Feb 26, 2026, 5:16 PM
updatedAt	Feb 26, 2026, 8:29 PM
githubUrl	https://github.com/neomjs/neo/issues/9313
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 26, 2026, 8:29 PM

Header Canvas: Fix layout syncing on mobile and dynamic item sizing

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

Closed v12.0.0 bugai

tobiu commented on Feb 26, 2026, 5:16 PM

The header canvas currently relies heavily on the overall toolbar size to update its visual capture state. This leads to issues:

Mobile Orientation Change: When using Chrome DevTools device mode, changing orientation does not correctly trigger a canvas update to recalculate the positions of the toolbar buttons.
Dynamic Item Loading (e.g., Logo): If a child item (like the logo) loads asynchronously and changes its width/dimensions without changing the overall toolbar dimensions, the header canvas doesn't notice the layout shift, resulting in misaligned capture rectangles behind the buttons.

We need to analyze how we are observing the toolbar and its items to ensure the canvas correctly updates its 'holes' behind the buttons when internal sizes change.

tobiu assigned to @tobiu on Feb 26, 2026, 5:16 PM

tobiu added the bug label on Feb 26, 2026, 5:16 PM

tobiu added the ai label on Feb 26, 2026, 5:16 PM

tobiu referenced in commit 5119f60 - "Header Canvas: Fix layout syncing on mobile and dynamic item sizing (#9313) on Feb 26, 2026, 8:29 PM

tobiu Feb 26, 2026, 8:29 PM

Input from Gemini 3.1 Pro:

✦ I have pushed the patch to dev. This implementation replaces the broken debounce timeouts with a strict async queue lock, combines the getDomRect queries, adds resize listeners to the buttons themselves, and overrides getObserverId to observe the parent Toolbar. This ensures that dynamic layout shifts and rapid window resizing are handled smoothly without worker bridge flooding, while always capturing the final layout frame.

As discussed, the underlying event routing architecture in SharedCanvas is not ideal and requires a follow-up ticket. I am closing this ticket as the immediate regression is resolved.

tobiu closed this issue on Feb 26, 2026, 8:29 PM

tobiu cross-referenced by #9314 on Feb 26, 2026, 8:31 PM