Replace Copilot CLI MCP env values with ${NAME} host interpolation
Copilot CLI v1.0.108 passes local MCP env values literally. Switch those entries to ${NAME}, add Windows sandbox.userPolicy.filesystem.enumeratePaths, use /index tgrep indexing, and unique-name SDK tools so MCP, sandbox, and search keep working.Why this loop
Interactive Copilot CLI sessions now pass local MCP server environment values literally, so previously interpolated host secrets or paths are sent as raw strings unless you write ${NAME}. That silently breaks local MCP. The same release restarts a sandboxed local MCP server after /cd so it uses the new directory's denied paths, persists /mcp disable across sessions, and makes /mcp enable honor repository settings that disable a server. Windows users can grant enumerate-only directory access with sandbox.userPolicy.filesystem.enumeratePaths in settings.json. Eligible repositories get managed shared tgrep indexing by default, plus /index commands. Creating, resuming, or replacing SDK tools with two custom tools of the same name is now an error (the model used to see the first definition while some SDKs ran the last handler). Update MCP env, sandbox grants, indexing, and tool names together so agents keep the intended filesystem posture and tools.
Proposed actions
- In each local MCP server env block used by Copilot CLI interactive sessions, replace expanded host values with ${NAME} (for example ${GITHUB_TOKEN} or ${HOME}) so the CLI interpolates from the host environment instead of sending the literal string.
- In settings.json, add sandbox.userPolicy.filesystem.enumeratePaths listing the Windows directories that should be enumerate-only grants rather than full filesystem access.
- In eligible repositories, run /index so managed shared tgrep indexing is used (v1.0.108 enables it by default for eligible repos).
- With the sandbox on, use /cd to move the session; a running local MCP server is now restarted so it follows the new directory's denied paths instead of keeping those of the directory the session left. Treat /mcp disable as persistent across sessions, and do not expect /mcp enable to turn on a server that repository settings disable.
- When creating, resuming, or replacing tools on an SDK session, give every custom tool a unique name; two tools with the same name now error instead of offering the first definition while some SDKs run the last handler.
Agent prompt
Paste into your agent or query via MCP (get_agent_prompt) — free, no extra AI costAGENTS.md / CLAUDE.md / GEMINI.md rule update
DevAgentRadar → Repo Harness Rule Patch
Goal: update our repository's permanent harness instructions based on this release.
Update the file that tool actually reads. Do not dump everything into one file.
- Claude Code → CLAUDE.md plus
.claude/(skills, hooks, settings, agents, commands). It does not read AGENTS.md natively; start CLAUDE.md with@AGENTS.md. - Codex, Copilot, Cursor, Factory Droid, Grok Build, Roo Code, Goose, OpenCode, Amp, Zed, Aider → AGENTS.md.
- Gemini CLI / Antigravity → GEMINI.md. AGENTS.md only if
context.fileNameis set. - Cursor glob-scoped rules →
.cursor/rules/*.mdc(plain.mdis ignored), not a second constitution. - Codex MCP →
.codex/config.toml, not.mcp.json. - Copilot extra instructions →
.github/copilot-instructions.md; custom agents →.github/agents/. - Windsurf →
.windsurf/rules(do not assume AGENTS.md). - Cline →
.clinerules. - Procedures → a skill (
SKILL.md). Enforcement the model must not skip → a hook. Isolated roles → subagents. - Do not fork the same rule into three tool files.
Context
Assistant: GitHub Copilot CLI Proposal: Replace Copilot CLI MCP env values with ${NAME} host interpolation Summary: Copilot CLI v1.0.108 passes local MCP env values literally. Switch those entries to ${NAME}, add Windows sandbox.userPolicy.filesystem.enumeratePaths, use /index tgrep indexing, and unique-name SDK tools so MCP, sandbox, and search keep working. Primary source: https://github.com/github/copilot-cli/releases/tag/v1.0.108
Why it matters
Interactive Copilot CLI sessions now pass local MCP server environment values literally, so previously interpolated host secrets or paths are sent as raw strings unless you write ${NAME}. That silently breaks local MCP. The same release restarts a sandboxed local MCP server after /cd so it uses the new directory's denied paths, persists /mcp disable across sessions, and makes /mcp enable honor repository settings that disable a server. Windows users can grant enumerate-only directory access with sandbox.userPolicy.filesystem.enumeratePaths in settings.json. Eligible repositories get managed shared tgrep indexing by default, plus /index commands. Creating, resuming, or replacing SDK tools with two custom tools of the same name is now an error (the model used to see the first definition while some SDKs ran the last handler). Update MCP env, sandbox grants, indexing, and tool names together so agents keep the intended filesystem posture and tools.
Suggested actions
- In each local MCP server env block used by Copilot CLI interactive sessions, replace expanded host values with ${NAME} (for example ${GITHUB_TOKEN} or ${HOME}) so the CLI interpolates from the host environment instead of sending the literal string.
- In settings.json, add sandbox.userPolicy.filesystem.enumeratePaths listing the Windows directories that should be enumerate-only grants rather than full filesystem access.
- In eligible repositories, run /index so managed shared tgrep indexing is used (v1.0.108 enables it by default for eligible repos).
- With the sandbox on, use /cd to move the session; a running local MCP server is now restarted so it follows the new directory's denied paths instead of keeping those of the directory the session left. Treat /mcp disable as persistent across sessions, and do not expect /mcp enable to turn on a server that repository settings disable.
- When creating, resuming, or replacing tools on an SDK session, give every custom tool a unique name; two tools with the same name now error instead of offering the first definition while some SDKs run the last handler.
Config surfaces this release may change
- settings files (high confidence) — check your repo before applying
- MCP servers (high confidence) — check your repo before applying
- skills (high confidence) — check your repo before applying
- subagent definitions (high confidence) — check your repo before applying
- sandbox settings — check your repo before applying
- background and headless runs — check your repo before applying
- hooks — check your repo before applying
After you finish
Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.
Tell the human: open https://devagentradar.com/proposals/github-copilot-cli-v1-0-108-replace-copilot-cli-mcp-env-values-with-name and mark Applied, Skipped, or Failed. Proposal id: 48b166b8-c143-4a70-8114-adef899319ec
Instructions:
- Read the existing context files and settings for the tools in this repo.
- Draft an explicit Git diff. Update ONLY agent harness rules or tool configuration.
- Call out deprecated flags, obsolete habits, or changed permission boundaries.
- Do not touch application logic.
Start with the proposed diff and say which layer and which tool's file it belongs in.
Your loop
This browser · no sign-in · not shared as “you”After you run the prompt
Only you can mark this. Agents cannot write your loop.
Your decision stays on this device. A public tally appears after a few votes.