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	7114
title	Neo gridcontainer example has rendering issues on chrome/android
state	Closed
labels	bug
assignees	[]
createdAt	Jul 27, 2025, 12:07 AM
updatedAt	Jul 27, 2025, 9:43 PM
githubUrl	https://github.com/neomjs/neo/issues/7114
author	TristanJamesBall
commentsCount	4
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jul 27, 2025, 12:50 PM

Neo gridcontainer example has rendering issues on chrome/android

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

Closed v10.1.0 bug

TristanJamesBall commented on Jul 27, 2025, 12:07 AM

Describe the bug Bar graph and buttons initially render correctly, then after a few seconds redraw to overlap.

To Reproduce Just opened the first example https://neomjs.com/dist/production/examples/grid/bigData/index.html

Expected behavior A clear and concise description of what you expected to happen.

Screenshots

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information): Samsung galaxy tab s7 Google Chrome 138.0.7204.168 (Official Build) (64-bit) Revision 3e8d82e86e9f508e88ed406c2a24657a6c691d30-refs/branch-heads/7204@{#2081} OS Android 13; SM-T870 Build/TP1A.220624.014; 33; REL APK versionCode 720416833 APK targetSdkVersion 35 Google Play services SDK=252225000; Installed=252635029; Access=1p JavaScript V8 13.8.258.29 User agent Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36 Command Line --top-controls-show-threshold=0.27 --top-controls-hide-threshold=0.17 --enable-viewport --validate-input-event-stream --enable-longpress-drag-selection --touch-selection-strategy=direction --disable-composited-antialiasing --enable-dom-distiller --flag-switches-begin --flag-switches-end Executable Path No such file or directory Profile Path /data/user/0/com.android.chrome/app_chrome/Default Additional context Add any other context about the problem here. I saw a blog article about neo.mjs , got curious, found the website and this is the first example I looked at, as it was near the top of the list and apropos to my job as a dba.

TristanJamesBall added the bug label on Jul 27, 2025, 12:07 AM

tobiu Jul 27, 2025, 12:16 AM

@TristanJamesBall Thanks a lot for the report!

I can confirm the issue, even on desktop:

https://github.com/user-attachments/assets/6b81b653-f721-43d7-83b5-03237e88c8bb

Definitely a regression bug in v10. It looks like on the first resize or scroll, component based columns can duplicate. It seems to get stable after scrolling more, but I need to look into what is happen in detail. Might be related to the new vdom aggregation logic.

TristanJamesBall Jul 27, 2025, 12:28 AM

Super quick and polite response to a drive by bug report - honestly that carries as much weight in my head as 10 fancy examples. Kudos, and thankyou.

Fwiw, I thought it might have something todo with the UI and font zoom settings I use, but it persists even with of that turned off. Given you've reproduced anyway this is probably moot but :

tobiu referenced in commit 789f1cb - "Neo gridcontainer example has rendering issues on chrome/android #7114" on Jul 27, 2025, 12:40 PM

tobiu Jul 27, 2025, 12:50 PM

@TristanJamesBall I think I got it now.

Funny story: I burned 6M Gemini 2.5 Pro Tokens on it, but it was leading nowhere. The real fix was just touching 5 lines of code, but it was very complex indeed.

In a nutshell: the v10 vdom aggregation was using neo-ignore placeholders, which did override existing componentIds. This was leading to cases where when an update cycle starts, the vdom (new state) contained the cell component, the vnode however included the neo-ignore flag. It was not getting the right cmp id back.

So, the change is to just move the flag into a new attribute.

Regarding "being polite". This should be inside the neo code of conduct, and it makes sense anyway: With opening a bug ticket, you are giving me the chance to fix a bug which I did not notice before => enabling me to fix it, and this improves the framework for everyone who is using it.

Best regards, Tobi

tobiu closed this issue on Jul 27, 2025, 12:50 PM

tobiu Jul 27, 2025, 9:43 PM

@TristanJamesBall forgot to mention: https://neomjs.com/dist/production/examples/grid/bigData/index.html

=> The new version is deployed now. Please let me know if you encounter any other issues. I also fixed the grid column header drag&drop resorting. You can over-drag to the left or right and the grid will scroll accordingly.