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	9315
title	Main Thread: Hardware-Sync ResizeObserver with requestAnimationFrame
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Feb 26, 2026, 9:59 PM
updatedAt	Feb 26, 2026, 10:00 PM
githubUrl	https://github.com/neomjs/neo/issues/9315
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 26, 2026, 10:00 PM

Main Thread: Hardware-Sync ResizeObserver with requestAnimationFrame

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

Closed v12.0.0 enhancementai

tobiu commented on Feb 26, 2026, 9:59 PM

The main.addon.ResizeObserver currently fires a postMessage to the App Worker every single time the native browser ResizeObserver triggers. During continuous layout thrashing (e.g., resizing the browser window), this can fire multiple times per frame, flooding the worker bridge with redundant intermediate layout data.

While the App Worker can defend against this (e.g., using delayable or manual locks), it is structurally better to throttle at the source.

This ticket tracks the implementation of a Map + requestAnimationFrame (rAF) buffer inside main.addon.ResizeObserver.

The Map ensures that if multiple elements resize, or an element resizes multiple times before a paint, we only retain the final state for each unique node.
The rAF lock ensures we only dispatch the accumulated postMessage payload exactly once per physical display frame (vsync), establishing a global protective dam for the App Worker.

tobiu added the enhancement label on Feb 26, 2026, 9:59 PM

tobiu added the ai label on Feb 26, 2026, 9:59 PM

tobiu referenced in commit 36a91ef - "Main Thread: Hardware-Sync ResizeObserver with requestAnimationFrame (#9315) on Feb 26, 2026, 9:59 PM

tobiu Feb 26, 2026, 9:59 PM

Input from Gemini 3.1 Pro:

✦ I have pushed the architectural enhancement to dev.

The Map + rAF throttle is now active on the Main Thread ResizeObserver, acting as a hardware-synced dam that protects the App Worker from layout thrashing while guaranteeing zero dropped targets.

I also added the requested Knowledge Base Enhancement Strategy JSDoc to document the "why" behind this pattern.

I will close this ticket.

tobiu assigned to @tobiu on Feb 26, 2026, 9:59 PM

tobiu closed this issue on Feb 26, 2026, 10:00 PM