// Use when moving between VS Code and Copilot CLI in the same session — transfers context between environments so you don't lose state when switching from editor to terminal.
Use when Copilot CLI's built-in tools do not cover a service you need — for example PostgreSQL, Redis, Jira, Slack, or an internal API — and you need to add an MCP server beyond the default GitHub MCP. NOT when the built-in tools already cover the task.
Use when designing or reviewing an AI agent system that needs policy-based access controls, intent classification, tool-level rate limiting, trust scoring for multi-agent workflows, or append-only audit trails.
Use when auditing an AI agent system against the OWASP Agentic Security Initiative Top 10 — checks tool access, prompt boundaries, memory handling, and operational safeguards across the agent pipeline.
Use when you need to evaluate an LLM pipeline or AI feature systematically — sets up an eval harness with test cases, scoring rubrics, and pass/fail tracking rather than one-off manual spot-checks
Use when reviewing or planning QA strategy for a feature, PR, or release so test coverage, test quality, reliability, and defect reporting are handled as a coherent engineering discipline instead of ad hoc checks.
Use when creating or validating a Git branch name so the branch follows a conventional type/description format, matches the work being done, and starts from the right base branch.
| name | ide-switching |
| description | Use when moving between VS Code and Copilot CLI in the same session — transfers context between environments so you don't lose state when switching from editor to terminal. |
| metadata | {"category":"copilot-exclusive","copilot_feature":"VS Code integration, shared Copilot subscription, unified context model"} |
GitHub Copilot exists in both VS Code and the terminal under a single subscription and unified platform. You can start a conversation in VS Code's Copilot Chat, switch to the CLI for batch automation, and return to VS Code for visual debugging — all with the same model access, same MCP servers, and same GitHub integration. Claude Code is terminal-only with no IDE counterpart; switching contexts means losing your AI assistant entirely.
| Task | VS Code Copilot | Copilot CLI |
|---|---|---|
| Visual code review | ✅ Side-by-side diffing | ❌ |
| Breakpoint debugging | ✅ Debug panel | ❌ |
| Single-file inline edits | ✅ Inline suggestions | ✅ Edit tool |
| Multi-file refactoring | ⚠️ Limited | ✅ Fleet mode |
| CI/CD debugging | ❌ | ✅ Actions MCP tools |
| PR review & management | ⚠️ Basic | ✅ Full GitHub MCP |
| Batch test execution | ⚠️ Manual | ✅ Background agents |
| SQL-based task tracking | ❌ | ✅ Session database |
| Multi-model selection | ⚠️ Limited | ✅ 20+ models available |
| Terminal automation | ⚠️ Integrated terminal | ✅ Native |
code .Keep the CLI workspace config in .mcp.json, and mirror the same server definitions into any
editor-specific config you standardize on:
// .mcp.json
{
"servers": {
"my-api": {
"command": "npx",
"args": ["my-api-mcp-server"],
"env": { "API_KEY": "${env:MY_API_KEY}" }
}
}
}
Treat the workspace config as the CLI-facing source of truth, then keep editor integrations aligned with the same server definitions.
# Step 1: CLI - Rename across the codebase
# "Rename the UserService class to AuthService in all files under src/"
# Copilot uses fleet agents to process files in parallel
# Step 2: VS Code - Visual review
code .
# Review changes in Source Control panel, check diff views
# Step 3: CLI - Run tests and fix issues
# "Run the full test suite and fix any failures from the rename"
# Start in CLI for triage
# "List my open PRs, check CI status, and summarize review comments"
# Switch to VS Code for focused coding
code src/feature.ts
# Use Copilot Chat inline for suggestions
# Back to CLI for PR creation
# "Create a PR for this branch with a description based on my commits"
.mcp.json, then mirror the
same server definitions into any editor-specific config your team uses.code <file> from CLI
to open specific files for visual inspection.