Enable Fusion tier, sandbox extensions, and COPILOT_SESSION_CWD in Copilot CLI 1.0.106
v1.0.106 adds a Fusion tier setting incopilot config, Sandbox extensions, COPILOT_SESSION_CWD for LSP/MCP, /code to open the session in VS Code, a searchable /settings dashboard, opt-in session @mentions, and GPT-6.1 Terra when available. Wire these into daily CLI use.Why this loop
Copilot CLI 1.0.106 changes how you bill, sandbox, and attach tools: Fusion tier is now a copilot config setting, extension processes can run inside the sandbox, and COPILOT_SESSION_CWD is how LSP and local MCP configs launch and expand paths (including relative cwd and session-directory filesystem permissions). Interactive workflow also changed: /code opens the current session in VS Code, /settings is a unified dashboard with global search, and session-management tools plus @mentions are opt-in for local sessions. The model picker can offer GPT-6.1 Terra under New models and now shows context-window size for flat, unpriced, and single-tier models. Skipping the upgrade leaves MCP servers on the wrong cwd, extensions outside the sandbox, no Fusion tier, and manual IDE handoff. After install, run copilot help config—it now lists previously missing settings such as askUser, effortLevel, planModel, toolSearch, and worktreeBaseRef. Do not infer anything from the 29 omitted changelog lines.
Proposed actions
- Install GitHub Copilot CLI v1.0.106 from https://github.com/github/copilot-cli/releases/tag/v1.0.106, then run
copilot help configand set the Fusion tier setting plus the Sandbox extensions setting so extension processes run inside the sandbox. - In the shell that launches Copilot CLI,
export COPILOT_SESSION_CWD="$(pwd)"(repo or session root) so LSP and local MCP server configs launch and expand relative paths from that directory, then restart the CLI. - In an interactive session, run
/settings, use global search for session management, and enable the opt-in session management tools so you can @mention other opted-in local sessions. - When you need the editor, type
/codein the current Copilot CLI session to open that session in VS Code instead of copying context by hand. - Open the model picker, select GPT-6.1 Terra under New models if it is available on your account, and use the displayed context window size when choosing flat, unpriced, or single-tier models.
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: Enable Fusion tier, sandbox extensions, and COPILOT_SESSION_CWD in Copilot CLI 1.0.106
Summary: v1.0.106 adds a Fusion tier setting in copilot config, Sandbox extensions, COPILOT_SESSION_CWD for LSP/MCP, /code to open the session in VS Code, a searchable /settings dashboard, opt-in session @mentions, and GPT-6.1 Terra when available. Wire these into daily CLI use.
Primary source: https://github.com/github/copilot-cli/releases/tag/v1.0.106
Why it matters
Copilot CLI 1.0.106 changes how you bill, sandbox, and attach tools: Fusion tier is now a copilot config setting, extension processes can run inside the sandbox, and COPILOT_SESSION_CWD is how LSP and local MCP configs launch and expand paths (including relative cwd and session-directory filesystem permissions). Interactive workflow also changed: /code opens the current session in VS Code, /settings is a unified dashboard with global search, and session-management tools plus @mentions are opt-in for local sessions. The model picker can offer GPT-6.1 Terra under New models and now shows context-window size for flat, unpriced, and single-tier models. Skipping the upgrade leaves MCP servers on the wrong cwd, extensions outside the sandbox, no Fusion tier, and manual IDE handoff. After install, run copilot help config—it now lists previously missing settings such as askUser, effortLevel, planModel, toolSearch, and worktreeBaseRef. Do not infer anything from the 29 omitted changelog lines.
Suggested actions
- Install GitHub Copilot CLI v1.0.106 from https://github.com/github/copilot-cli/releases/tag/v1.0.106, then run
copilot help configand set the Fusion tier setting plus the Sandbox extensions setting so extension processes run inside the sandbox. - In the shell that launches Copilot CLI,
export COPILOT_SESSION_CWD="$(pwd)"(repo or session root) so LSP and local MCP server configs launch and expand relative paths from that directory, then restart the CLI. - In an interactive session, run
/settings, use global search for session management, and enable the opt-in session management tools so you can @mention other opted-in local sessions. - When you need the editor, type
/codein the current Copilot CLI session to open that session in VS Code instead of copying context by hand. - Open the model picker, select GPT-6.1 Terra under New models if it is available on your account, and use the displayed context window size when choosing flat, unpriced, or single-tier models.
Config surfaces this release may change
- background and headless runs (high confidence) — check your repo before applying
- hooks (high confidence) — check your repo before applying
- settings files (high confidence) — check your repo before applying
- MCP servers — check your repo before applying
- permission rules — check your repo before applying
- skills — 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-106-enable-fusion-tier-sandbox-extensions-and-co and mark Applied, Skipped, or Failed. Proposal id: 29fdf4bb-cf16-4fd6-b763-8e4725a0546f
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.