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	8591
title	Centralize TreeList expand and scroll logic to fix deep linking
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Jan 13, 2026, 12:01 PM
updatedAt	Jan 13, 2026, 12:22 PM
githubUrl	https://github.com/neomjs/neo/issues/8591
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 13, 2026, 12:21 PM

Centralize TreeList expand and scroll logic to fix deep linking

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

Closed v11.21.0 enhancementai

tobiu commented on Jan 13, 2026, 12:01 PM

Problem: A recent optimization in Neo.tree.List (removing DOM for collapsed folders) broke the "deep linking" scroll behavior in the Portal app. Controllers currently implement inconsistent and brittle workarounds (manual timeouts or polling waitForDomRect) to handle expanding parents and scrolling to the newly mounted item.

Solution:

Implement a robust expandAndScrollToItem(itemId) method in Neo.tree.List that handles the expansion, waits for the DOM node to be mounted (using waitForDomRect), and then scrolls it into view.
Refactor MainContainerController for Blog, Release, and Tickets in the Portal app to use this new method, ensuring consistency and reliability.

Files to Modify:

src/tree/List.mjs
apps/portal/view/news/blog/MainContainerController.mjs
apps/portal/view/news/release/MainContainerController.mjs
apps/portal/view/news/tickets/MainContainerController.mjs

tobiu added the enhancement label on Jan 13, 2026, 12:01 PM

tobiu added the ai label on Jan 13, 2026, 12:01 PM

tobiu referenced in commit 745fd9c - "feat: Centralize TreeList expand and scroll logic to fix deep linking (#8591)" on Jan 13, 2026, 12:21 PM

tobiu assigned to @tobiu on Jan 13, 2026, 12:21 PM

tobiu closed this issue on Jan 13, 2026, 12:21 PM

tobiu Jan 13, 2026, 12:22 PM

Input from Gemini 3 Pro:

✦ Implemented Neo.tree.List.expandAndScrollToItem(itemId) to centralize the logic for deep linking. Refactored Portal.view.news.blog.MainContainerController, Portal.view.news.release.MainContainerController, and Portal.view.news.tickets.MainContainerController to use this new method.

Changes pushed to dev.

Follow-up issues identified regarding horizontal scrolling and header styling will be tracked in a separate ticket.