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	9105
title	Refactor: DevRank Viewport Lazy Loading & Routing
state	Closed
labels	airefactoringperformance
assignees	tobiu
createdAt	Feb 11, 2026, 11:23 PM
updatedAt	Feb 11, 2026, 11:58 PM
githubUrl	https://github.com/neomjs/neo/issues/9105
author	tobiu
commentsCount	1
parentIssue	8930
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 11, 2026, 11:58 PM

Refactor: DevRank Viewport Lazy Loading & Routing

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

Closed v12.0.0 airefactoringperformance

tobiu commented on Feb 11, 2026, 11:23 PM

Refactor DevRank Viewport for lazy loading and better routing architecture.

Tasks:

Create apps/devrank/view/home/MainContainer.mjs to encapsulate the Home view (Grid + Controls).
Update apps/devrank/view/Viewport.mjs:
- Use lazy loading (module: () => import(...)) for Home and Learn views.
- Remove activeIndex: 0 to allow the controller to handle routing.
Update apps/devrank/view/ViewportController.mjs:
- Add defaultHash: '/home'.

Reason: To improve initial load time and align with the Portal architecture.

tobiu added the ai label on Feb 11, 2026, 11:23 PM

tobiu added the refactoring label on Feb 11, 2026, 11:23 PM

tobiu added the performance label on Feb 11, 2026, 11:23 PM

tobiu referenced in commit 0ee3597 - "Fix: Viewport activeIndex & TreeList store loading race condition (#9105)" on Feb 11, 2026, 11:57 PM

tobiu assigned to @tobiu on Feb 11, 2026, 11:58 PM

tobiu Feb 11, 2026, 11:58 PM

Input from Gemini 3 Pro:

✦ I have successfully refactored the DevRank.view.Viewport for lazy loading and routing, and fixed a critical race condition in Neo.app.content.TreeList.

Changes:

Lazy Loading: Created apps/devrank/view/home/MainContainer.mjs and updated Viewport.mjs to use module: () => import(...) for both Home and Learn views.

Routing Fix: Set activeIndex: null in Viewport card layout and removed mainContentLayouts from ViewportController, allowing the controller to handle initial routing via defaultHash.

Race Condition Fix (TreeList): Updated src/app/content/TreeList.mjs to:

Check for Neo.isFunction(this.store?.load) in doLoadStore to prevent crashes when the store is not yet initialized.

Trigger doLoadStore in afterSetStore if contentPath is already set, ensuring the store loads even if the path was set before the store binding completed.

This ensures robust initialization and prevents double loading in other app sections (like Portal Releases) by checking this.contentPath before auto-loading in afterSetStore.

tobiu added parent issue #8930 on Feb 11, 2026, 11:58 PM

tobiu closed this issue on Feb 11, 2026, 11:58 PM