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	8477
title	Refactor Progress Component ID handling
state	Closed
labels	airefactoringcore
assignees	tobiu
createdAt	Jan 9, 2026, 6:14 PM
updatedAt	Jan 9, 2026, 6:19 PM
githubUrl	https://github.com/neomjs/neo/issues/8477
author	tobiu
commentsCount	1
parentIssue	8469
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 9, 2026, 6:19 PM

Refactor Progress Component ID handling

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

Closed v11.19.1 airefactoringcore

tobiu commented on Jan 9, 2026, 6:14 PM

Context: src/component/Progress.mjs uses afterSetId to update the for attribute of its label to match the component ID.

    afterSetId(value, oldValue) {
        super.afterSetId(value, oldValue);

        this.label.for = value;
        this.update()
    }

This is a standard DOM synchronization task. However, running it in afterSetId (before initConfig completes) triggers the prototype pollution risk (though mitigated by the construct fix, it's still cleaner to avoid).

Goal: Refactor afterSetId into ensureStableIds. Since ensureStableIds is called during VDOM updates (and initial creation), it's the perfect place to ensure structural attributes like for are synchronized with the ID.

Verification:

Create test/playwright/unit/component/Progress.spec.mjs.
Verify label.for matches component.id.
Verify changing id updates label.for.

tobiu added the ai label on Jan 9, 2026, 6:14 PM

tobiu added the refactoring label on Jan 9, 2026, 6:14 PM

tobiu added the core label on Jan 9, 2026, 6:14 PM

tobiu added parent issue #8469 on Jan 9, 2026, 6:14 PM

tobiu referenced in commit 1c2f6a7 - "refactor: replace afterSetId with ensureStableIds in Progress component (#8477)" on Jan 9, 2026, 6:17 PM

tobiu assigned to @tobiu on Jan 9, 2026, 6:18 PM

tobiu Jan 9, 2026, 6:19 PM

Input from Gemini 3 Pro:

✦ I have refactored src/component/Progress.mjs to use ensureStableIds instead of afterSetId.

Changes:

Replaced afterSetId with ensureStableIds.

Moved the this.label.for = this.id logic into ensureStableIds.

This ensures the for attribute is always synchronized with the component ID during VDOM updates, without the need for manual update() calls or prototype pollution risks.

Verification:

Added test/playwright/unit/component/Progress.spec.mjs.

Verified that the label.for attribute correctly matches the component ID initially and after runtime changes.

Commit: 1c2f6a725 (#8477)

tobiu closed this issue on Jan 9, 2026, 6:19 PM