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	7448
title	Create DocumentHead Addon with Canonical URL Support
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Oct 10, 2025, 10:09 PM
updatedAt	Nov 11, 2025, 11:59 AM
githubUrl	https://github.com/neomjs/neo/issues/7448
author	tobiu
commentsCount	2
parentIssue	7446
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Nov 11, 2025, 11:59 AM

Create DocumentHead Addon with Canonical URL Support

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

Closed v11.1.0 enhancementai

tobiu commented on Oct 10, 2025, 10:09 PM

To solve the critical duplicate content issue caused by the SPA architecture and multiple deployment environments (dev, prod, esm), a main thread addon is required to dynamically manage the document's <head>.

This is the highest priority task for the SEO epic, as it enables crawlers like Google to correctly index our content by providing a canonical URL.

Acceptance Criteria

Create a new main thread addon at src/main/addon/DocumentHead.mjs.
The addon must expose the following RMA methods:
- setTitle(newTitle): Updates the content of the <title> tag.
- setTag(tagObject): A smart method that creates or updates a <meta> or <link> tag. It should remove any existing tag with the same name or property before adding the new one.
- setCanonical(url): A dedicated method that creates or updates the <link rel="canonical" href="..."> tag.
The portal application controller (apps/portal/view/ViewportController.mjs) must be updated to:
- Listen for route changes.
- On route change, call the HeadManager addon's methods to update the title, meta description, and, most importantly, the canonical URL for the new route.

tobiu assigned to @tobiu on Oct 10, 2025, 10:09 PM

tobiu added the enhancement label on Oct 10, 2025, 10:09 PM

tobiu added the ai label on Oct 10, 2025, 10:09 PM

tobiu added parent issue #7446 on Oct 10, 2025, 10:09 PM

22Yash Oct 17, 2025, 4:36 PM

@tobiu I would like to work on this issue!

I understand this is a high-priority SEO task requiring the creation of a Main Thread Addon to dynamically manage the document content, specifically to fix the duplicate content issue by setting the canonical URL.

My plan is:

Implement src/main/addon/HeadManager.mjs: Implement the setTitle, setTag (with logic to find/remove duplicates by name/property/rel), and setCanonical methods, ensuring all are accessible via RMA (Remote Method Access).
Integrate in ViewportController.mjs: Implement the logic in apps/portal/view/ViewportController.mjs to listen for route changes and call the new HeadManager methods (especially setCanonical) to update the head metadata for the new route.

Please assign this to me. Thank you!

tobiu changed title from Create HeadManager Addon with Canonical URL Support to Create DocumentHead Addon with Canonical URL Support on Nov 11, 2025, 10:02 AM

tobiu Nov 11, 2025, 10:11 AM

@22Yash sorry, missed your comment. the v11 release was insane. since this was already last month, i will tackle this one on my own.

tobiu referenced in commit 0d13b56 - "#7448 base class" on Nov 11, 2025, 10:11 AM

tobiu referenced in commit 6cd886c - "#7448 class name" on Nov 11, 2025, 10:12 AM

tobiu referenced in commit 9134cf4 - "#7448 getCanonical, getTag, setCanonical, setTag, Portal.view.ViewportController WIP" on Nov 11, 2025, 10:52 AM

tobiu referenced in commit e721456 - "#7448 Portal.view.ViewportController" on Nov 11, 2025, 11:30 AM

tobiu referenced in commit 1dc41c6 - "#7448 main.addon.DocumentHead: getLdJson, setLdJson" on Nov 11, 2025, 11:45 AM

tobiu referenced in commit d1417ee - "#7448 main.addon.DocumentHead: refactoring & cleanup" on Nov 11, 2025, 11:56 AM

tobiu referenced in commit 72c5260 - "#7448 main.addon.DocumentHead: intent driven JSDoc comments" on Nov 11, 2025, 11:59 AM

tobiu closed this issue on Nov 11, 2025, 11:59 AM