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	8391
title	Update generateSeoFiles.mjs to handle tree-structured release data
state	Closed
labels	bugdocumentationbuild
assignees	tobiu
createdAt	Jan 7, 2026, 7:32 PM
updatedAt	Jan 7, 2026, 7:50 PM
githubUrl	https://github.com/neomjs/neo/issues/8391
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 7, 2026, 7:41 PM

Update generateSeoFiles.mjs to handle tree-structured release data

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

Closed v11.19.0 bugdocumentationbuild

tobiu commented on Jan 7, 2026, 7:32 PM

The apps/portal/resources/data/releases.json structure was recently refactored from a simple flat list to a flat-tree structure (including parent nodes for major versions) to support the Portal's TreeList component.

The buildScripts/generateSeoFiles.mjs script, specifically the getLlmsTxt function, consumes this JSON to generate the "Latest Updates" section. Currently, it iterates over the array without filtering, which causes it to process the new parent nodes (e.g., "v11") as if they were release notes. Since these parent nodes lack the version, date, and title properties of actual release objects, this results in malformed entries or errors.

Task: Update buildScripts/generateSeoFiles.mjs to filter the releases array. It should exclude nodes where isLeaf is explicitly false (or check for the existence of the version property) before slicing the top 5 items for the SEO content.

Affected File:

buildScripts/generateSeoFiles.mjs

tobiu added the bug label on Jan 7, 2026, 7:32 PM

tobiu added the documentation label on Jan 7, 2026, 7:32 PM

tobiu added the build label on Jan 7, 2026, 7:32 PM

tobiu assigned to @tobiu on Jan 7, 2026, 7:33 PM

tobiu referenced in commit 3f0e48f - "fix(build): Filter release tree nodes in SEO generation (#8391) on Jan 7, 2026, 7:40 PM

tobiu closed this issue on Jan 7, 2026, 7:41 PM

tobiu Jan 7, 2026, 7:50 PM

Input from Gemini 3 Pro:

✦ Task completed.

Updated buildScripts/generateSeoFiles.mjs to filter out directory nodes (parent items without a version) from the release data. This ensures the llms.txt generation works correctly with the new tree-structured releases.json.