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	8064
title	Optimize LivePreview Renderer Loading & Lifecycle
state	Closed
labels	enhancementairefactoringarchitecture
assignees	tobiu
createdAt	Dec 9, 2025, 2:16 AM
updatedAt	Dec 9, 2025, 2:18 AM
githubUrl	https://github.com/neomjs/neo/issues/8064
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Dec 9, 2025, 2:17 AM

Optimize LivePreview Renderer Loading & Lifecycle

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

Closed v11.17.0 enhancementairefactoringarchitecture

tobiu commented on Dec 9, 2025, 2:16 AM

Optimize the renderer loading mechanism in Neo.code.LivePreview to prevent redundant module fetching and ensure smoother initialization.

Changes:

Renderer Caching: Implement a renderers object to cache instantiated renderers.
loadRenderer Method: Create a dedicated method to handle dynamic importing and caching.
initAsync Integration: Use initAsync to await the initial renderer load, ensuring isReady state reflects renderer availability.
Optimized afterSetLanguage: Update to only trigger loadRenderer on runtime changes (when oldValue exists).
Execution Guard: Update afterSetRenderer to only trigger doRunSource if this.value is truthy, handling edge cases of simultaneous config application.
Static Languages: Add static languages = ['markdown', 'neomjs'].
beforeSetLanguage: Implement validation against the static languages array.

Goal: Improve performance and robustness of the LivePreview component when switching languages and initializing.

tobiu added the enhancement label on Dec 9, 2025, 2:16 AM

tobiu added the ai label on Dec 9, 2025, 2:16 AM

tobiu added the refactoring label on Dec 9, 2025, 2:16 AM

tobiu added the architecture label on Dec 9, 2025, 2:16 AM

tobiu assigned to @tobiu on Dec 9, 2025, 2:16 AM

tobiu referenced in commit db5ba73 - "Optimize LivePreview Renderer Loading & Lifecycle #8064" on Dec 9, 2025, 2:17 AM

tobiu closed this issue on Dec 9, 2025, 2:17 AM

tobiu Dec 9, 2025, 2:18 AM

Input from Gemini:

✦ Refactoring complete.

Changes:

Optimization: Implemented renderers cache in LivePreview.mjs to avoid redundant imports.

loadRenderer: Added method for efficient dynamic loading and caching.

Initialization: Updated initAsync to await initial renderer load.

Lifecycle: Updated afterSetLanguage to handle runtime changes only.

Robustness: Added && this.value check in afterSetRenderer to prevent execution on empty values.

Validation: Added static languages array and beforeSetLanguage validation method.

Verified code changes.