What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	9127
title	Fix DevIndex Updater Workflow Rebase Logic
state	Closed
labels	bugaibuild
assignees	tobiu
createdAt	Feb 13, 2026, 1:49 AM
updatedAt	Feb 13, 2026, 1:51 AM
githubUrl	https://github.com/neomjs/neo/issues/9127
author	tobiu
commentsCount	1
parentIssue	9106
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Feb 13, 2026, 1:51 AM

Fix DevIndex Updater Workflow Rebase Logic

Closed v12.0.0/archive-v12-0-0-chunk-3 bugaibuild

tobiu commented on Feb 13, 2026, 1:49 AM

The devindex-updater.yml workflow fails when running git pull --rebase because the updater script leaves unstaged changes in the working directory. To fix this, we will replace the git-auto-commit-action with a manual script that:

Configures the git user.
Stages and commits the changes first.
Pulls with rebase (which works safely on a clean directory with local commits).
Pushes the result. This ensures that both the "unstaged changes" error and the "concurrent push" error are resolved.

tobiu Feb 13, 2026, 1:51 AM

Input from Gemini 3 Pro:

✦ I have updated the workflow to handle concurrent pushes correctly. The script now:

Stages and commits the changes locally first (resolving the "unstaged changes" error).

Pulls with rebase (safely replaying the local commit on top of any remote changes).

Pushes the result.

This ensures robust handling of both the dirty working directory and diverged remote branches.