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	6116
title	component.Base: vdom => flag => ref
state	Open
labels	enhancementno auto close
assignees	tobiu
createdAt	Nov 18, 2024, 12:03 PM
updatedAt	Jun 13, 2025, 2:23 AM
githubUrl	https://github.com/neomjs/neo/issues/6116
author	tobiu
commentsCount	4
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]

component.Base: vdom => flag => ref

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

Openenhancementno auto close

tobiu commented on Nov 18, 2024, 12:03 PM

minor breaking change.

inside the component tree, we are using reference as identifiers. inside the vdom tree we are using flag. this feels a bit inconsistent.

it might be confusing to use the exact same name (2 different trees, controller.getReference() will not search inside the vdom), so i think ref would be a good alternative.

tobiu added the enhancement label on Nov 18, 2024, 12:03 PM

tobiu assigned to @tobiu on Nov 18, 2024, 12:03 PM

tobiu reopened this issue on Mar 3, 2025, 8:30 AM

tobiu removed the stale label on Mar 3, 2025, 8:30 AM

tobiu added the no auto close label on Mar 3, 2025, 8:30 AM

tobiu Mar 3, 2025, 8:30 AM

this ticket is supposed to stay open.

tobiu Jun 13, 2025, 2:23 AM

Input from Gemini:

Your proposal to change flag to ref within the vdom markup, despite it being a breaking change and necessitating the removal of flag, makes a lot of sense and I would strongly support it.

Here's why:

Unified Mental Model: This is the most compelling reason. Using ref consistently across the framework, whether you're referring to a component instance in the component tree (reference on a component config, then accessed via lookupReference) or a specific virtual DOM node within a component's vdom (ref property on a vdom node, then accessed via a helper method like getVdomNodeByRef), creates a much more cohesive and intuitive mental model for developers. "Ref" universally implies "I want a programmatic reference to this specific item."

Reduced Cognitive Load: While flag avoids immediate collision with reference, introducing a separate concept for a very similar purpose (getting a programmatic handle) can actually increase cognitive load in the long run. Unifying under ref simplifies the API surface developers need to learn and remember.

Familiarity for Newcomers: Many popular VDOM-based frameworks (like React) use ref for similar purposes (getting a reference to a DOM node or component). This familiar terminology could ease the onboarding process for developers coming from other ecosystems.

Improved Readability: ref is concise and widely understood in the context of getting references to UI elements.

Regarding the "breaking change" aspect: You're correct that supporting both flag and ref simultaneously for the same purpose makes no sense. A clean break, deprecating flag entirely and migrating to ref, is the right approach. For a framework like Neo.mjs, which prioritizes architectural elegance and performance, occasional breaking changes that lead to significant long-term API improvements are often justifiable, provided they are clearly documented with migration paths.

Implementation Considerations: If you make this change, it would be beneficial to:

Update the proposed getVdomNodeByFlag helper: Rename it to something like getVdomNodeByRef or queryVdomRef, to align with the new property name. Clear Documentation: Explicitly state the deprecation of flag and the new usage of ref in migration guides and documentation, clearly distinguishing how ref is used in vdom vs. reference is used for component instances (if reference remains separate). However, the conceptual overlap is much smaller now.