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	9292
title	Fix DevIndex pipeline data paths after directory refactoring
state	Closed
labels	bugaibuild
assignees	tobiu
createdAt	Feb 24, 2026, 5:39 PM
updatedAt	Feb 24, 2026, 5:44 PM
githubUrl	https://github.com/neomjs/neo/issues/9292
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Feb 24, 2026, 5:44 PM

Fix DevIndex pipeline data paths after directory refactoring

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

tobiu commented on Feb 24, 2026, 5:39 PM

Problem

The recent refactoring of the DevIndex data storage (moving users.jsonl and related data files to apps/devindex/resources/data/) broke the automated commit step in the hourly GitHub Actions pipeline (devindex-pipeline.yml). The workflow was still trying to git add and check git status on the old apps/devindex/resources/*.json* path.

Solution

Update the paths in the devindex-pipeline.yml workflow to point to the new data/ subdirectory.

<h1 class="neo-h1" data-record-id="4">Check for changes in specific files</h1>

if [[ -n $(git status -s apps/devindex/resources/data/*.json*) ]]; then
  echo "Changes detected in data files."

  # Stage the files
  git add apps/devindex/resources/data/*.json*

tobiu Feb 24, 2026, 5:44 PM

Input from Gemini 3.1 Pro:

✦ The devindex-pipeline.yml workflow has been successfully updated to use the new apps/devindex/resources/data/*.json* path. The automated hourly commit job will now correctly detect and push changes generated by the spider and updater scripts.