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	8461
title	Fix Portal Release buttons missing text due to missing name field
state	Closed
labels	airefactoring
assignees	tobiu
createdAt	Jan 9, 2026, 12:37 PM
updatedAt	Jan 9, 2026, 12:48 PM
githubUrl	https://github.com/neomjs/neo/issues/8461
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 9, 2026, 12:48 PM

Fix Portal Release buttons missing text due to missing name field

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

Closed v11.19.1 airefactoring

tobiu commented on Jan 9, 2026, 12:37 PM

The Portal App's PageContainer (shared view) currently hardcodes the property name to populate the text of the 'Previous' and 'Next' navigation buttons. However, Portal.model.Release does not use name, but relies on id or title for identification, and we want to use id for the button text in this context.

Fix:

Refactor PageContainer: Introduce a buttonTextField config (defaulting to 'name') to allow customizing which field is used for button text.
Pass Config: Ensure this config is passed down from Portal.view.shared.content.Container.
Configure Releases: In Portal.view.news.release.MainContainer, set buttonTextField to 'id'.
Clean up StateProvider: Remove unused previousPageText and nextPageText variables in Portal.view.news.release.MainContainerStateProvider.

tobiu added the ai label on Jan 9, 2026, 12:37 PM

tobiu added the refactoring label on Jan 9, 2026, 12:37 PM

tobiu referenced in commit 8ff67ed - "fix: Restore Portal Release navigation button text (#8461)" on Jan 9, 2026, 12:47 PM

tobiu assigned to @tobiu on Jan 9, 2026, 12:48 PM

tobiu Jan 9, 2026, 12:48 PM

Input from tobiu:

◆ Refactoring complete.

Changes Implemented:

Portal.view.shared.content.PageContainer:

Added buttonTextField config (default: 'name').

Updated afterSetNextPageRecord and afterSetPreviousPageRecord to use dynamic field access.

Portal.view.shared.content.Container:

Added buttonTextField config.

Passed it down to the PageContainer item in construct().

Portal.view.news.release.MainContainer:

Set buttonTextField: 'id' to correctly display release versions (e.g., "11.19.0") instead of undefined.

Portal.view.news.release.MainContainerStateProvider:

Cleaned up unused nextPageText and previousPageText variables.

This restores the navigation button text for Release Notes while maintaining the correct behavior for other content types (like Guides) that rely on the default name field.

tobiu closed this issue on Jan 9, 2026, 12:48 PM