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	10248
title	Document Fresh MCP Client Isolation Strategy for cache bypass
state	Closed
labels	documentationenhancementaiarchitectureneeds-re-triage
assignees	[]
createdAt	Apr 23, 2026, 6:27 PM
updatedAt	3:19 PM
githubUrl	https://github.com/neomjs/neo/issues/10248
author	neo-gemini-pro
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 6, 2026, 11:53 PM

Document Fresh MCP Client Isolation Strategy for cache bypass

Closed v13.0.0/archive-v13-0-0-chunk-5 documentationenhancementaiarchitectureneeds-re-triage

neo-gemini-pro commented on Apr 23, 2026, 6:27 PM

Context

During debugging of the MailboxService.from tool-shape validation issue, Gemini successfully bypassed stale MCP cache issues by spawning a fresh MCP server via ai/mcp/client.

The Problem

Agents operating on MCP servers they themselves are connected to suffer from stale cache windows. If they modify an MCP tool definition, their own connection does not see the fresh tool shape, leading to ghost debugging loops.

The Architectural Reality

The ai/mcp/client primitive allows spawning a fresh client that bypasses the agent's stale MCP cache. This is a crucial substrate primitive for agent self-repair, but it is currently not formally documented as a debugging strategy.

The Fix

Update the .agent/skills/debugging-antigravity/SKILL.md (or relevant skill) to formally document the "Fresh MCP Client Isolation Strategy".

Explain the stale cache problem for agents testing their own MCP servers.
Document the ai/mcp/client script usage as the empirical substrate for verifying fresh tool shapes.

Acceptance Criteria

Update debugging-antigravity skill to include the Fresh MCP Client Isolation Strategy.
Add warnings about ghost debugging loops caused by stale MCP caches.

Origin Session ID

Origin Session ID: 1c5933cc-a2d0-4296-ae3f-f4e815d385a2