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	8688
title	Fix: Correct Default Expansion Logic (Revert Release, Apply to Ticket Index)
state	Closed
labels	bugaibuild
assignees	tobiu
createdAt	Jan 15, 2026, 1:39 PM
updatedAt	Jan 15, 2026, 1:46 PM
githubUrl	https://github.com/neomjs/neo/issues/8688
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 15, 2026, 1:46 PM

Fix: Correct Default Expansion Logic (Revert Release, Apply to Ticket Index)

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

Closed v11.22.0 bugaibuild

tobiu commented on Jan 15, 2026, 1:39 PM

Goal: Correct the default expansion logic in the build scripts.

Correction: The previous change to buildScripts/createReleaseIndex.mjs was incorrect; the intention was to apply this logic to the Ticket Index (buildScripts/createTicketIndex.mjs) because the first group in Tickets is "Backlog" (which should be collapsed), whereas the first group in Releases is the latest version (which should likely be expanded, or maybe the user wants Releases to stay as is).

Tasks:

Revert buildScripts/createReleaseIndex.mjs: Set expansion back to index === 0.
Update buildScripts/createTicketIndex.mjs: Change expansion logic to expand index === 1 (the first real release) and collapse index === 0 ("Backlog").

tobiu added the bug label on Jan 15, 2026, 1:39 PM

tobiu added the ai label on Jan 15, 2026, 1:39 PM

tobiu added the build label on Jan 15, 2026, 1:39 PM

tobiu referenced in commit cf89c80 - "fix: Correct default expansion logic for Release and Ticket indices (#8688)" on Jan 15, 2026, 1:42 PM

tobiu assigned to @tobiu on Jan 15, 2026, 1:43 PM

tobiu Jan 15, 2026, 1:46 PM

Input from Gemini 3 Pro:

✦ I have corrected the default expansion logic in the build scripts.

Changes:

Reverted buildScripts/createReleaseIndex.mjs: The Release Notes tree now correctly expands the first major version group (index 0) by default.

Updated buildScripts/createTicketIndex.mjs: The Ticket tree now expands the second group (index 1, the latest release) by default, keeping the "Backlog" (index 0) collapsed.

Data Regeneration: Both releases.json and tickets.json have been updated with the correct collapsed states.

This ensures the user experience is intuitive: Release Notes show the latest version immediately, while Tickets hide the Backlog to focus on the active release work.

tobiu closed this issue on Jan 15, 2026, 1:46 PM