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	7910
title	Enhancement: Update SEO generator to support middleware-compatible routes
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Nov 29, 2025, 11:11 AM
updatedAt	Nov 29, 2025, 12:44 PM
githubUrl	https://github.com/neomjs/neo/issues/7910
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Nov 29, 2025, 12:41 PM
milestone	11.12.0

Enhancement: Update SEO generator to support middleware-compatible routes

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

Closed v11.12.0 enhancementai

tobiu commented on Nov 29, 2025, 11:11 AM

The buildScripts/generateSeoFiles.mjs script needs to be updated to support the new middleware routing strategy.

Currently, the sitemap generator produces hash-based URLs (e.g., https://neomjs.com/#/services), which is suboptimal for SEO. The middleware will handle "real" routes (e.g., https://neomjs.com/services) and map them to client-side routes.

Tasks:

Update getSitemapXml and getLlmsTxt to generate "real routes" (without the hash fragment) for the <loc> tags and content links.
Add a new output format (e.g., json or objects) to the CLI that outputs an array of route objects. Each object should contain:
- route: The real route (e.g., /services)
- clientSideRoute: The hash-based route (e.g., /#/services) This will allow the middleware to easily resolve URLs and determine the correct client-side route state.

tobiu added the enhancement label on Nov 29, 2025, 11:11 AM

tobiu added the ai label on Nov 29, 2025, 11:11 AM

tobiu assigned to @tobiu on Nov 29, 2025, 11:11 AM

tobiu referenced in commit adc10e4 - "Enhancement: Update SEO generator to support middleware-compatible routes #7910" on Nov 29, 2025, 12:05 PM

tobiu Nov 29, 2025, 12:06 PM

Input from Gemini:

✦ I have refactored the route generation logic in buildScripts/generateSeoFiles.mjs to rely on explicit categories instead of brittle string matching (like .html extensions).

Changes:
Categorized Routes: Routes are now classified as tree (documentation), top-level (SPA pages), or file (examples/apps).

Correct Pathing:

file routes (examples) are treated as absolute paths (e.g., /apps/colors/index.html) and do not get prefixed with /learn.

Their clientSideRoute is correctly set to an empty string "", as they are standalone entry points, not hash-based routes within the main app.
Verified Output:
node buildScripts/generateSeoFiles.mjs --format objects now produces the correct structure:
{
  "route": "/apps/colors/index.html",
  "clientSideRoute": ""
}
Documentation routes (e.g., /learn/benefits/Introduction) are also correctly generated with their corresponding hash-based clientSideRoute (/#/learn/benefits/Introduction).

tobiu closed this issue on Nov 29, 2025, 12:41 PM

tobiu added this to the 11.12.0 milestone on Nov 29, 2025, 12:44 PM