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	8138
title	Support saveScrollPosition in DomApiRenderer
state	Closed
labels	enhancementaicore
assignees	tobiu
createdAt	Dec 17, 2025, 3:19 PM
updatedAt	Dec 19, 2025, 10:56 AM
githubUrl	https://github.com/neomjs/neo/issues/8138
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Dec 19, 2025, 10:56 AM

Support saveScrollPosition in DomApiRenderer

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

Closed v11.17.0 enhancementaicore

tobiu commented on Dec 17, 2025, 3:19 PM

Context

Ticket #8137 introduced scrollTop and scrollLeft as top-level properties on Neo.vdom.VNode to enable preserving scroll state. These properties are currently applied in Neo.main.DeltaUpdates for the updateNode action.

Problem

The insertNode action, which utilizes Neo.main.render.DomApiRenderer when Neo.config.useDomApiRenderer is true, does not currently respect these properties. As a result, when a component is re-mounted (e.g. moved in the DOM or restored from a cached state), its previous scroll position is lost.

Goal

Update Neo.main.render.DomApiRenderer to check for and apply scrollTop and scrollLeft properties from the vnode to the created DOM element.

Implementation Details

Modify src/main/render/DomApiRenderer.mjs:
- In createDomTree, after creating the DOM element, check if vnode.scrollTop or vnode.scrollLeft are present.
- If so, apply them to the domNode.

tobiu added the enhancement label on Dec 17, 2025, 3:19 PM

tobiu added the ai label on Dec 17, 2025, 3:19 PM

tobiu added the core label on Dec 17, 2025, 3:19 PM

tobiu assigned to @tobiu on Dec 17, 2025, 3:20 PM

tobiu Dec 17, 2025, 3:39 PM

Input from Gemini 2.5:

✦ I have implemented the requested changes in src/main/render/DomApiRenderer.mjs.

Key Implementation Detail: I introduced a Post-Mount Queue pattern. Standard browser behavior prevents setting scrollTop or scrollLeft on detached DOM nodes (nodes not yet inserted into the document) because they lack a layout box and overflow context.

To solve this, the createDomTree method now:

Collects any nodes with scrollTop or scrollLeft properties into a postMountUpdates queue during the recursive build phase.

Inserts the fully built tree into the live DOM.

Immediately iterates through the queue to apply the scroll values now that the nodes have a valid rendering context.

This ensures that scroll positions are correctly restored when components are re-mounted or moved.

tobiu referenced in commit bae9034 - "feat: Support saveScrollPosition in DomApiRenderer #8138" on Dec 17, 2025, 3:48 PM

tobiu cross-referenced by #8139 on Dec 17, 2025, 3:55 PM

tobiu closed this issue on Dec 19, 2025, 10:56 AM