COPILOT CLI 1.0.10 LANDS STABILITY, /UNDO, MULTI-SESSION, AND SAFER MCP/PLUGIN LOADING FOR BIG REPOS
GitHub shipped Copilot CLI 1.0.10 with concrete stability, safety, and workflow upgrades that make it better for large repos and remote sessions. The [1.0.10 r...
GitHub shipped Copilot CLI 1.0.10 with concrete stability, safety, and workflow upgrades that make it better for large repos and remote sessions.
The 1.0.10 release trims memory when opening huge files, fixes remote login and working directory issues, and adds an /undo command that reverts the last turn’s file changes. It also introduces experimental multiple concurrent sessions, repairs repo hooks in .github/hooks/ for prompt mode, and tightens MCP loading by deferring workspace servers from .mcp.json, .vscode/mcp.json, and devcontainer.json until folder trust is confirmed. Plugin manifests in .claude-plugin/ or .plugin/ now load their MCP and LSP servers correctly.
In a real-world take, running Copilot from the terminal avoids VS Code resource contention in massive monorepos. Elio Struyf shows the CLI running as a separate process while still tapping your editor’s context when available post.
Teams asking for “agent plugins” have a community path today via MCP and repository-scoped configuration in Copilot discussion. Pair that with repository Custom Instructions to steer suggestions toward your conventions guide.
CLI 1.0.10 reduces friction for big-monorepo work and remote sessions while adding safer, more predictable repo-scoped tooling via MCP.
Undo, multi-session, and fixed hooks make AI-assisted changes less risky and easier to operationalize across teams.
-
terminal
Benchmark Copilot CLI vs VS Code Chat on a large repo: responsiveness, memory, and end-to-end time for multi-file refactors.
-
terminal
Enable .github/hooks/ prompts and workspace MCP via .mcp.json; verify trust gating, plugin manifest loading, and /undo behavior.
Legacy codebase integration strategies...
- 01.
Shift heavy codegen and refactors to Copilot CLI for large repos; keep editor responsive while retaining context from VS Code.
- 02.
Pilot MCP servers behind folder trust; restrict sensitive tools and confirm remote /login works across SSH, WSL, and Codespaces.
Fresh architecture paradigms...
- 01.
Bootstrap repos with Custom Instructions, .github/hooks/, and a minimal .mcp.json to standardize conventions from day one.
- 02.
Document CLI workflows (/undo, model picker policy, sessions) and bake them into devcontainers and CI guardrails.