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	9360
title	scroll to bottom bug on main page
state	Closed
labels	bug
assignees	tobiu
createdAt	Mar 6, 2026, 10:21 AM
updatedAt	Mar 7, 2026, 3:42 PM
githubUrl	https://github.com/neomjs/neo/issues/9360
author	Marcklarso
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 7, 2026, 3:42 PM

scroll to bottom bug on main page

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

Closed v12.1.0 bug

Marcklarso commented on Mar 6, 2026, 10:21 AM

the view wont stop at the bottom of the main page

To Reproduce Steps to reproduce the behavior:

Go to https://neomjs.com/#/home
Scroll down to bottom of the page
Page will not stay at the bottom but jump up to position shown in screenshot

Expected behavior I expect the page to stay at the bottom.

Screenshots will jump up to this position

Desktop

OS: Windows 11 Pro
Browser chrome
Version 145.0.7632.117

Marcklarso added the bug label on Mar 6, 2026, 10:21 AM

tobiu referenced in commit 46d1f45 - "fix: scroll to bottom bug on main page (#9360)" on Mar 7, 2026, 3:40 PM

tobiu assigned to @tobiu on Mar 7, 2026, 3:40 PM

tobiu Mar 7, 2026, 3:42 PM

Input from Gemini 3.1 Pro:

✦ Hi @Marcklarso, thank you for reporting this issue!

The bug where the portal page jumped up when trying to scroll to the bottom on Windows has been fixed.

The AiToolchain view, which includes the FooterContainer, inherited scroll-snap-align: center. When trying to scroll to the very bottom, Windows Chrome was forcefully snapping the view back to the center of the AiToolchain container because the combined content is taller than the viewport.

To fix this:

Changed the scroll-snap-align of AiToolchain to start, allowing users to scroll freely downwards once the view snaps to the top.

Added scroll-snap-align: end to the FooterContainer so that when the bottom of the page is reached, the browser recognizes it as a valid snap point and does not attempt to snap back upwards.

The changes have been pushed to the dev branch.

tobiu closed this issue on Mar 7, 2026, 3:42 PM