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	9379
title	Mobile Scrollbar UX: Increase touch width to 40px and theme thumb colors
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Mar 7, 2026, 6:56 PM
updatedAt	Mar 7, 2026, 7:09 PM
githubUrl	https://github.com/neomjs/neo/issues/9379
author	tobiu
commentsCount	1
parentIssue	9369
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 7, 2026, 7:09 PM

Mobile Scrollbar UX: Increase touch width to 40px and theme thumb colors

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

Closed v12.1.0 enhancementai

tobiu commented on Mar 7, 2026, 6:56 PM

Follow-up to Epic #9369

In resolving the invisible WebKit scrollbar thumb on mobile (#9376), we had to explicitly define ::-webkit-scrollbar-thumb styling. Currently, the background-color is hardcoded to a neutral grey. Additionally, the touch target width (24px) is too small for comfortable grabbing according to mobile HIG standards.

Tasks:

Extract the hardcoded thumb color into theme-specific CSS variables (--grid-scrollbar-thumb-color).
Increase the --grid-scrollbar-touch-width from 24px to 40px to provide a massive, reliable touch hitbox for the "scrub bar" interaction.
Update the thumb's transparent border to 8px so the visual thumb remains sleek (24px visual width) inside the massive 40px invisible container.

tobiu added the enhancement label on Mar 7, 2026, 6:56 PM

tobiu added the ai label on Mar 7, 2026, 6:56 PM

tobiu added parent issue #9369 on Mar 7, 2026, 6:57 PM

tobiu assigned to @tobiu on Mar 7, 2026, 7:07 PM

tobiu referenced in commit 5874338 - "feat(Grid): enhance mobile scrollbar UX with 40px touch targets and themed colors (#9379)" on Mar 7, 2026, 7:08 PM

tobiu Mar 7, 2026, 7:08 PM

Input from Gemini 3.1 Pro:

✦ I have completed the UX upgrades for the mobile scrollbar!

Massive Touch Target: The body.neo-has-touch environment now expands the vertical scrollbar container and the ::-webkit-scrollbar width to 40px (via --grid-scrollbar-touch-width). This aligns with mobile accessibility guidelines for touch targets.

Sleek Visuals: To prevent the thumb from looking comically huge inside a 40px track, I added an 8px transparent border (background-clip: padding-box). The visual thumb is a sleek 24px wide, but the invisible touchable area remains 40px.

Themed Colors: The hardcoded grey fallback is gone. All 5 themes now provide a --grid-scrollbar-thumb-color that matches their respective dark/light palettes (e.g., translucent white for neo-dark).

WebKit Bug Fix: The inner spacer div is explicitly set to 10px. This tricks the mobile WebKit emulator into recognizing enough content width to paint the thumb, but avoids hitting the right-edge boundary that triggers the "corner intersection artifact".

A note on Thumb Height: In the Chrome DevTools mobile emulator, the thumb height might still appear incredibly small (or invisible) when viewing 50,000 rows. This is because WebKit calculates native thumb height based on the containerHeight / contentHeight ratio, and the emulator often fails to enforce a reasonable minimum height. Real iOS/Android devices have robust OS-level minimum thumb sizes for accessibility. We will test these changes on physical hardware to confirm if the OS-level minimum height kicks in as expected. If not, a pure DOM-based custom "Scrub Bar" component might be the final evolution for massive datasets.

Closing this ticket!

tobiu closed this issue on Mar 7, 2026, 7:09 PM