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	9119
title	DevIndex: Add Scheduled Hourly Updater Workflow
state	Closed
labels	enhancementaibuild
assignees	tobiu
createdAt	Feb 12, 2026, 9:31 PM
updatedAt	Feb 12, 2026, 9:32 PM
githubUrl	https://github.com/neomjs/neo/issues/9119
author	tobiu
commentsCount	1
parentIssue	9106
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Feb 12, 2026, 9:32 PM

DevIndex: Add Scheduled Hourly Updater Workflow

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

tobiu commented on Feb 12, 2026, 9:31 PM

This task implements a scheduled GitHub Actions workflow to keep the DevIndex data fresh.

Objective: Run the DevIndex.services.Updater automatically on an hourly basis to update user profiles and contribution stats.

Strategy:

Schedule: Hourly (cron: '0 * * * *').
Batch Size: Limit to 200 users per run.
- Rationale: This stays safely within the 1,000 req/hour limit for public repositories, even accounting for 2-4x retry logic on errors.
- Throughput: ~4,800 updates/day -> ~3 day full refresh cycle for 15k users.
Persistence: The workflow will commit changes to users.jsonl and tracker.json back to the dev branch.

Implementation:

Create .github/workflows/devindex-updater.yml
Use stefanzweifel/git-auto-commit-action for reliable committing.
Use concurrency to prevent overlapping runs.

tobiu Feb 12, 2026, 9:32 PM

Input from Gemini 3 Pro:

✦ I have implemented the scheduled workflow in .github/workflows/devindex-updater.yml.

Configuration:

Schedule: Hourly (0 * * * *).

Command: npm run devindex:update -- --limit=200

Safety: concurrency group ensures only one update runs at a time.

Persistence: Uses git-auto-commit-action to push changes to users.jsonl and tracker.json back to the dev branch.

This setup should robustly handle the "Safe 200" batch size, maintaining index freshness without risking rate limits.

2026-07-23T08:47:17Z @neo-gpt-emmy cross-referenced by #15745