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	7744
title	Refactor Release Preparation Script: Rename `injectPackageVersion` to `prepareRelease` and Integrate SEO File Generation
state	Closed
labels	enhancementairefactoring
assignees	tobiu
createdAt	Nov 11, 2025, 1:05 PM
updatedAt	Nov 11, 2025, 2:02 PM
githubUrl	https://github.com/neomjs/neo/issues/7744
author	tobiu
commentsCount	0
parentIssue	7446
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Nov 11, 2025, 2:02 PM

Refactor Release Preparation Script: Rename `injectPackageVersion` to `prepareRelease` and Integrate SEO File Generation

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

Closed v11.1.0 enhancementairefactoring

tobiu commented on Nov 11, 2025, 1:05 PM

The current buildScripts/injectPackageVersion.mjs script is responsible for updating the package version across various files during a release. This ticket proposes to refactor and enhance this script to create a more comprehensive release preparation tool.

Proposed Changes:

Rename Script: Rename buildScripts/injectPackageVersion.mjs to buildScripts/prepareRelease.mjs (or a similar, more descriptive name). This new name will better reflect its expanded responsibilities.
Update package.json: Modify the package.json scripts to use the new script name.
Integrate SEO File Generation: Extend the functionality of the prepareRelease.mjs script to automatically regenerate sitemap.xml and llm.txt. This ensures that these SEO-critical files are always up-to-date with the latest content and version information as part of the release process. The script should call the relevant functions from generate-seo-files.mjs to perform this.

Benefits:

Streamlines the release workflow.
Ensures consistency and accuracy of version numbers and SEO files.
Reduces the risk of manual errors during release preparation.

Acceptance Criteria:

The script buildScripts/injectPackageVersion.mjs is renamed to buildScripts/prepareRelease.mjs.
All references to the old script name in package.json are updated.
The prepareRelease.mjs script successfully updates package versions and regenerates sitemap.xml and llm.txt when executed.
The generated sitemap.xml and llm.txt files contain the correct, canonical, hash-based URLs.

tobiu assigned to @tobiu on Nov 11, 2025, 1:05 PM

tobiu added the enhancement label on Nov 11, 2025, 1:05 PM

tobiu added the ai label on Nov 11, 2025, 1:05 PM

tobiu added the refactoring label on Nov 11, 2025, 1:05 PM

tobiu added parent issue #7446 on Nov 11, 2025, 1:06 PM

tobiu referenced in commit b466aea - "Refactor Release Preparation Script: Rename injectPackageVersion to prepareRelease and Integrate SEO File Generation #7744" on Nov 11, 2025, 1:25 PM

tobiu closed this issue on Nov 11, 2025, 2:02 PM