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	9294
title	Revert to PAT for cross-repo pages deployment to fix 403 error
state	Closed
labels	bugaibuild
assignees	tobiu
createdAt	Feb 24, 2026, 6:55 PM
updatedAt	Feb 24, 2026, 7:08 PM
githubUrl	https://github.com/neomjs/neo/issues/9294
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 24, 2026, 7:08 PM

Revert to PAT for cross-repo pages deployment to fix 403 error

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

Closed v12.0.0 bugaibuild

tobiu commented on Feb 24, 2026, 6:55 PM

Problem

The DevIndex automated pipeline's new step to push the users.jsonl file to the neomjs/pages repository failed with a 403 Forbidden error: remote: Permission to neomjs/pages.git denied to github-actions[bot].

This confirms that despite both repositories being in the same organization, the default GITHUB_TOKEN generated during the neo workflow run does not have implicit cross-repository write access.

Solution

Revert the token configuration in the devindex-pipeline.yml workflow back to using a dedicated Personal Access Token (PAGES_DEPLOY_PAT).

This PAT must be configured as a repository secret within the neo repository and must belong to a user/bot account with write access to the neomjs/pages repository. A guard clause is also included to gracefully skip the push step if the secret is not defined, preventing the entire pipeline from failing.

tobiu added the bug label on Feb 24, 2026, 6:55 PM

tobiu added the ai label on Feb 24, 2026, 6:55 PM

tobiu added the build label on Feb 24, 2026, 6:55 PM

tobiu referenced in commit 82fb1cb - "build: Revert to PAT for cross-repo pages deployment to fix 403 error (#9294)" on Feb 24, 2026, 7:03 PM

tobiu assigned to @tobiu on Feb 24, 2026, 7:08 PM

tobiu Feb 24, 2026, 7:08 PM

Input from Gemini 3.1 Pro:

✦ I have reverted the cross-repository push logic back to using the PAGES_DEPLOY_PAT secret, bypassing the default GITHUB_TOKEN which does not grant cross-organization write access.

The workflow now includes a guard clause if [ -z "$PAGES_DEPLOY_PAT" ] that skips the push gracefully instead of throwing an error if the secret has not been configured in the repository yet.

The fix has been rebased and pushed to dev.

tobiu closed this issue on Feb 24, 2026, 7:08 PM