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	13626
title	Local Agent OS graph goes stale: syncGithubWorkflow isn''t an orchestrator task + PrimaryRepoSync skips (no-configured-roots) → golden path computes on old state
state	Closed
labels	bugaiarchitectureperformancemodel-experience
assignees	neo-opus-grace
createdAt	Jun 20, 2026, 4:02 PM
updatedAt	3:20 PM
githubUrl	https://github.com/neomjs/neo/issues/13626
author	neo-opus-grace
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 21, 2026, 2:11 AM

Local Agent OS graph goes stale: syncGithubWorkflow isn't an orchestrator task + PrimaryRepoSync skips (no-configured-roots) → golden path computes on old state

Closed v13.1.0/archive-v13-1-0-chunk-4 bugaiarchitectureperformancemodel-experience

neo-opus-grace commented on Jun 20, 2026, 4:02 PM

Symptom

The LOCAL Agent OS golden path computes on stale state — it recommends #12633 over #13623 (which supersedes it), because recent GitHub content (tickets/pulls/discussions, incl. the #13621 → #13623 / #13624 no-hold-state graduation) is not in the graph gemma4 reads.

Root cause (V-B-A, 2026-06-20)

Two independent gaps leave the local graph's freshness dark:

syncGithubWorkflow is NOT an orchestrator-scheduled task. ai/daemons/orchestrator/taskDefinitions.mjs schedules session summarization, memory miniSummary backfill, kbSync (knowledge base sync), and primary checkout dev sync (PrimaryRepoSyncService) — but not the github-workflow content sync (ai:sync-github-workflow → ai/scripts/maintenance/syncGithubWorkflow.mjs). The only orchestrator github-workflow reference is SwarmHeartbeatService.mjs:15 (wake notifications, not content). So GitHub content reaches the local graph only on a manual npm run ai:sync-github-workflow.
PrimaryRepoSync skips with no-configured-roots (PrimaryRepoSyncService.mjs:356) — devSyncRoots (AiConfig.orchestrator.devSyncRoots / NEO_ORCHESTRATOR_DEV_SYNC_ROOTS) is unconfigured → the git dev-branch pull doesn't run (the operator's observed "no repo pulls/pushes").

Fix

Wire syncGithubWorkflow as a deployment-gated orchestrator task — enabled for the LOCAL Agent OS; the cloud / multi-tenant deployment uses its own tenant-ingestion (push/pull), so gate it like kbSync does via resolveDeploymentEnabled(...) (ADR 0014 task taxonomy — a local/shared sync, not a cloud-deployable one). Add to taskDefinitions.mjs + the scheduling pipeline + a githubSyncMs interval leaf.
Configure devSyncRoots (or document/confirm the intended local config) so PrimaryRepoSync runs — or confirm it's intentionally skipped locally.

Why it matters

Without a fresh graph, gemma4's golden path + the Dream pipeline operate on stale topology — every recent graduation / ticket / PR is invisible to the strategic recommendation. Local-Agent-OS-specific (the cloud deployment ingests differently), but load-bearing for night-shift self-direction.

Refs #13624 (orchestrator data-currency), ADR 0014 (deployment-aware scheduler task taxonomy). V-B-A by @neo-opus-grace per @tobiu (2026-06-20).