customizations-in-the-agent-host

Diagnose and fix customization enablement bugs in the agent host architecture.

10|1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/KevinHuangIsLearning/shortestpath-ide --skill customizations-in-the-agent-host-kevinhuangislearning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: customizations-in-the-agent-host
Source: https://github.com/KevinHuangIsLearning/shortestpath-ide/tree/main/.github/skills/customizations-in-the-agent-host
Command: npx skills add https://github.com/KevinHuangIsLearning/shortestpath-ide --skill customizations-in-the-agent-host-kevinhuangislearning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Customization enablement (plugins, MCP servers, agents, skills, instructions) in the agent host involves scoped decisions, overlay semantics, and per-provider enforcement that are easy to get wrong, causing bugs like disabled MCP servers still reaching the model or user decisions being silently erased. ## Core Features & Use Cases - Enablement mental model: Explains scoped decisions (Session, Workspace, Global), the client-base/host-overlay model, and identity rules for MCP server storage keys. - Debugging playbook: Ranks diagnostic signals (published objects, Agent Host.log tool_search overrides, UI, model claims) and provides a cross-session reproduction recipe. - Provider enforcement guide: Documents how Copilot, Claude, and Codex enforce enablement at launch and mid-session, including known traps like the not_configured status bug. - Use Case: A disabled MCP server still appears to the model; use this Skill to trace the publication path, verify resolution routing, and identify which of the known failure modes applies. ## Quick Start Ask the agent to use the customizations-in-the-agent-host skill to investigate why a disabled MCP server is still exposing tools to the model.

Frequently Asked Questions about customizations-in-the-agent-host

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why is a disabled MCP server still reaching the model?▼

A disabled MCP server reaches the model when a publication or SDK-handoff path skips resolveCustomizationEnablement and reads a stored snapshot instead. Check that every emit and handoff site routes through resolution, and verify the tool_search override entries in Agent Host.log.

How does customization enablement work in the agent host?▼

Enablement is an ordered list of scoped decisions (Session, Workspace, Global), most specific first, with absent entries inheriting from the next scope out. The client's value is the base and host decisions layer on top, storing only what differs from that base.

Who owns the Global enablement decision for a plugin's MCP server?▼

The host owns Global for anything it discovered, even inside a client-forwarded plugin; the client owns Global only for what it bundled. The discriminator is the childEnablement record, not clientId.

Why does a customization show pending and how should it be handled?▼

Pending means the session or working directory is not yet known, and SDK-boundary consumers must fail closed. Never default pending to enabled or cache the verdict; recompute and republish once the enablement service settles.

Can Codex enforce MCP server enablement mid-session?▼

No, Codex supplies MCP servers only at thread/start or resume, so mid-session enforcement is a documented limitation. Copilot and Claude support live enforcement via rpc.mcp.enable/disable and live reconcile respectively.