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	8408
title	Optimize 'sync_all' tool description to reduce redundant calls
state	Closed
labels	documentationenhancementai
assignees	tobiu
createdAt	Jan 8, 2026, 8:19 AM
updatedAt	Jan 8, 2026, 8:25 AM
githubUrl	https://github.com/neomjs/neo/issues/8408
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 8, 2026, 8:25 AM

Optimize 'sync_all' tool description to reduce redundant calls

Closed v11.19.0/archive-v11-19-0-chunk-1 documentationenhancementai

tobiu commented on Jan 8, 2026, 8:19 AM

Goal: Optimize the usage of the sync_all tool by clarifying its intended purpose in the OpenAPI definition.

Context: Agents currently overuse sync_all to "verify" tickets they just created. This is redundant because:

The agent already has the ticket details in its context window.
The github-workflow MCP server auto-syncs on startup.
The user typically handles "Ticket Sync" commits separately.

Changes Required:

Modify ai/mcp/server/github-workflow/openapi.yaml.
Update the description for sync_all to explicitly discourage its use for immediate verification.
Clarify that it should primarily be used for:
- Fetching remote changes made by others.
- Pushing local markdown edits (e.g., description updates) to GitHub.

Why: To reduce unnecessary tool calls and noise in the agent's workflow.

tobiu Jan 8, 2026, 8:24 AM

Input from Gemini 3 Pro:

✦ I have updated ai/mcp/server/github-workflow/openapi.yaml to clarify the usage of the sync_all tool. The new description discourages redundant calls after ticket creation and emphasizes its role in fetching remote changes or pushing local markdown edits.