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	8684
title	Bug: MagicMoveText corrupted state on view navigation
state	Closed
labels	bugai
assignees	tobiu
createdAt	Jan 15, 2026, 12:51 PM
updatedAt	Jan 15, 2026, 1:05 PM
githubUrl	https://github.com/neomjs/neo/issues/8684
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 15, 2026, 1:04 PM

Bug: MagicMoveText corrupted state on view navigation

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

Closed v11.22.0 bugai

tobiu commented on Jan 15, 2026, 12:51 PM

Investigate and fix "corrupted dom rect states" in Neo.component.MagicMoveText when navigating between views.

Symptoms: When navigating away from a view containing MagicMoveText and returning, the character positions can become corrupted, leading to visual glitches.

Analysis: The component relies on measureCache to store DOMRects for performance. This cache assumes that character positions for a given text string are constant as long as the font and container size don't change. However, during view transitions (e.g., CardLayout switches), the component might be hidden, resized, or moved. If contentWidth / contentHeight are stale, or if the ResizeObserver fires out of sync with the visibility change, the cache might return invalid positions.

Potential Solutions:

Cache Validation: Check if the cached rects match the current container context.
Lifecycle Invalidation: Aggressively clear cache on activate / show events if applicable.
Hybrid Strategy: Clear cache every N cycles or on specific triggers.
Force Remeasure: Add a config to disable caching for debugging or specific instances.

Goal: Make the component "bullet-proof" against layout thrashing and view navigation issues while maintaining performance where possible.

tobiu added the bug label on Jan 15, 2026, 12:51 PM

tobiu added the ai label on Jan 15, 2026, 12:51 PM

tobiu added the core label on Jan 15, 2026, 12:51 PM

tobiu referenced in commit cc29624 - "fix: Harden MagicMoveText measurement caching (#8684)" on Jan 15, 2026, 1:04 PM

tobiu assigned to @tobiu on Jan 15, 2026, 1:04 PM

tobiu Jan 15, 2026, 1:04 PM

Input from Gemini 3 Pro:

✦ Implemented smart caching in measureChars to validate cache against current dimensions. Added cacheClearInterval (defaulting to 10) to periodically refresh the cache, preventing long-term corruption from layout thrashing.

tobiu closed this issue on Jan 15, 2026, 1:04 PM

tobiu removed the core label on Jan 15, 2026, 1:05 PM