customizations-in-the-agent-host

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

1|Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Niiihuel/openide --skill customizations-in-the-agent-host-niiihuel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: customizations-in-the-agent-host
Source: https://github.com/Niiihuel/openide/tree/main/vscode/.github/skills/customizations-in-the-agent-host
Command: npx skills add https://github.com/Niiihuel/openide --skill customizations-in-the-agent-host-niiihuel

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 disabled servers to still reach the model or user decisions to be silently erased. ## Core Features & Use Cases - Enablement Architecture Guide: Explains the scoped decision list (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 gives a cross-session reproduction recipe. - Provider Enforcement Reference: 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 the stored decision, and identify which code path skipped resolveCustomizationEnablement(). ## Quick Start Ask the agent to explain why a disabled MCP server is still reaching the model and which enablement code path to inspect first.

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 the tool_search override lines in Agent Host.log and verify every emit path routes through resolution.

How does customization enablement work in the agent host?▼

Enablement is an ordered list of scoped decisions (Session, Workspace, Global), not a boolean. isCustomizationEnabled picks the first entry, absent entries inherit outward, and host decisions overlay the client-provided base rather than replacing it.

How do Copilot, Claude, and Codex differ in MCP server enforcement?▼

Copilot uses disabledMcpServers at launch plus rpc.mcp.enable/disable mid-session, Claude sets session options at materialize with live reconcile, and Codex only supplies servers at thread start with no mid-session changes possible.

Why does a customization show the wrong enabled state in the UI?▼

Wrong UI state usually comes from identity bugs where an MCP server key depends on tree position instead of owningPluginUri, or from caching a pending verdict. Use targetForMcpServer and recompute pending states rather than caching them.

What tests validate customization enablement changes?▼

Run npm run typecheck-client, the customizationEnablement unit tests via scripts/test.sh, and the agentHost integration tests for sessionConfig, toolApproval, codexCustomizations, and claudeAgent. The unit runner uses pre-compiled output, so typecheck must run separately.