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	8451
title	Move GitHub Workflow Sync Target to resources/content
state	Closed
labels	documentationenhancementai
assignees	tobiu
createdAt	Jan 9, 2026, 9:54 AM
updatedAt	Jan 9, 2026, 10:02 AM
githubUrl	https://github.com/neomjs/neo/issues/8451
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 9, 2026, 10:02 AM

Move GitHub Workflow Sync Target to resources/content

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

Closed v11.19.1 documentationenhancementai

tobiu commented on Jan 9, 2026, 9:54 AM

Move the GitHub workflow sync targets from .github/ to resources/content/ to enable deployment via GitHub Pages, as the .github folder is strictly filtered out by GitHub Pages.

Changes:

Move Directories:
- .github/ISSUE -> resources/content/issues
- .github/ISSUE_ARCHIVE -> resources/content/issue-archive
- .github/RELEASE_NOTES -> resources/content/release-notes
- .github/.sync-metadata.json -> resources/content/.sync-metadata.json
Update Configuration:
- Modify ai/mcp/server/github-workflow/config.mjs to point to the new paths.
Update .npmignore:
- Update .npmignore to exclude the new resources/content locations instead of the old .github ones, preventing bloat in the npm package.

tobiu added the documentation label on Jan 9, 2026, 9:54 AM

tobiu added the enhancement label on Jan 9, 2026, 9:55 AM

tobiu added the ai label on Jan 9, 2026, 9:55 AM

tobiu assigned to @tobiu on Jan 9, 2026, 10:02 AM

tobiu Jan 9, 2026, 10:02 AM

Input from Gemini 3 Pro:

✦ I have moved the GitHub workflow sync targets to resources/content/ to resolve the deployment issue with GitHub Pages.

Actions Taken:

Moved Directories:

.github/ISSUE -> resources/content/issues

.github/ISSUE_ARCHIVE -> resources/content/issue-archive

.github/RELEASE_NOTES -> resources/content/release-notes

.github/.sync-metadata.json -> resources/content/.sync-metadata.json

Updated Configuration:

Modified ai/mcp/server/github-workflow/config.mjs to point to the new locations.

Updated .npmignore:

Removed old .github paths and added resources/content/ paths to exclude them from the npm package.

The changes have been committed locally. Please push them to the remote repository.

tobiu closed this issue on Jan 9, 2026, 10:02 AM

tobiu cross-referenced by #8452 on Jan 9, 2026, 10:09 AM

tobiu referenced in commit b7bab05 - "feat: Move GitHub workflow sync target to resources/content (#8451)" on Jan 9, 2026, 10:11 AM