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	6859
title	Portal.view.blog.List: Clearing the filter no longer works
state	Closed
labels	bug
assignees	tobiu
createdAt	Jun 24, 2025, 11:33 AM
updatedAt	Jun 24, 2025, 4:40 PM
githubUrl	https://github.com/neomjs/neo/issues/6859
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jun 24, 2025, 4:40 PM

Portal.view.blog.List: Clearing the filter no longer works

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

Closed v10.0.0-beta.1 bug

tobiu commented on Jun 24, 2025, 11:33 AM

Deprecation issue: it did work fine before.
It is not related to the new useDomApiRenderer config => breaks in both modes.
It is related to the custom filterItems() logic.
Changing the logic to use removeDom instead of style.display = 'none' would help, but we need to find the root cause.
All items get parsed inside the filterItems() loop.
Logging the deltas reveals up to 300 delta OPs, trying to insert nodes and update the structure.
My guess is: If the vnode => vdom id sync had an issue, and we would get new auto-generated ids for parts of a list item, this would explain it.

Since this issue affects various areas of the framework, it is most likely a "tobi only" ticket.

I need to dive into it, before we can declare v10 as stable.

tobiu assigned to @tobiu on Jun 24, 2025, 11:33 AM

tobiu added the bug label on Jun 24, 2025, 11:33 AM

tobiu referenced in commit fa85510 - "Portal.view.blog.List: Clearing the filter no longer works #6859 => minor logic polishing" on Jun 24, 2025, 12:01 PM

tobiu changed title from Portal.view.blog.List: Clearning the filter no longer works to Portal.view.blog.List: Clearing the filter no longer works on Jun 24, 2025, 12:01 PM

tobiu referenced in commit 885872c - "Portal.view.blog.List: Clearing the filter no longer works #6859 => vdom.Helper typo fix" on Jun 24, 2025, 12:33 PM

tobiu referenced in commit d25166e - "#6859 Portal.view.blog.List: util.Style: compareStyles() => fixed an else if part without a return value" on Jun 24, 2025, 1:06 PM

tobiu Jun 24, 2025, 1:24 PM

this was a fascinating debugging session.

vdom.Helper: compareAttributes() contained a crazy bad typo:

                switch (prop) {
                    case 'attributes':
                        attributes = {};

                    Object.entries(value).forEach(([key, value]) =&gt; {
                        const
                            oldValue    = oldVnode.attributes[key],
                            hasOldValue = Object.hasOwn(oldVnode.attributes, &#39;key&#39;);

this obviously has to be:

                                hasOldValue = Object.hasOwn(oldVnode.attributes, key);

key lesson learned: never trust AI :)

This typo meant: every attribute which did NOT get changed returned a delta to change it to its same value, leading to a MASSIVE overhead of deltas in v10 afterwards.

I did not even notice it, since Neo can easily handle 40k deltas per second.

The second issue was inside the vdom.VNode interface: in v9, a vnode inside the vdom worker always contained style: {} in case there were no styles. To minify it, the styles property got removed in case it is empty in v10.

util.Style: compareStyles() had a bug when receiving undefined as the newValue, which is fixed now.

The key lesson learned: the entire auto-id on vnode level synchronization back to vdom structures works perfectly fine. I was a bit worried that this part broke => not the case.

tobiu closed this issue on Jun 24, 2025, 4:40 PM