This is a real guide, generated for an example user. Yours is built from a short interview about how you actually work — your saved prompts, your projects, your do-not-break workflows. Free during beta.
How to move from GitHub Copilot to Claude Code.
A step-by-step playbook to move GitHub Copilot workflows into Claude Code — copy-ready, checkable, and checked against each tool’s own docs.
- Prepared for
- An example 3-person marketing team
- Sources
- 14 verified sources
6 steps (5 core), 4 paste-ready assets, 10 to confirm in Claude Code.
- Curated repo context (Spaces)
- Copilot Chat in the IDE
- Agent mode multi-file edits
- Copilot CLI
Setup steps
Work through these in order. Check each off as you go; your progress is saved on this device.
Install Claude Code so it works alongside VS Code. Install the CLI, then add the VS Code extension which gives you a graphical Claude Code panel with inline diffs, plan-mode review, @-mentions with line ranges, session history, parallel conversations, and checkpoints. The same conversation history is shared between the CLI and the panel via `claude --resume`. Open VS Code, run `claude` once in the integrated terminal, and install the extension from the marketplace when prompted (it also works on Cursor/Windsurf/Kiro via Open VSX).
Vscode extensionImportant: Claude Code is a terminal-first agentic CLI, NOT an inline ghost-text completion engine. It does not provide AI tab completions as you type — code changes flow through the agent's Read/Write/Edit tools and a diff-review surface. Tab completion in Claude Code is shell-style (command names and file paths) and is a CLI-only feature, explicitly not available in the graphical panel. To preserve your "IDE inline completion" must-keep, leave GitHub Copilot's inline completion enabled in VS Code for ghost text, and use Claude Code for agentic multi-file work. Verify your team's policy on running both extensions side by side.
A few things to confirm
We flag these up front so nothing surprises you — a short list to double-check in Claude Code as you go.
- 10 items are flagged to confirm in Claude Code — check the menu paths and field names as you go.
- The one notable capability gap is inline ghost-text completion, which Claude Code does not provide; plan to retain Copilot for that.
Paste-ready assets
Workflows from GitHub Copilot, rewritten to paste straight into Claude Code.
Copilot Spaces bundling code, docs, specs, snippets, and custom instructions
# CLAUDE.md ## Project overview <one-paragraph description of the repo and its purpose> ## Key files & where things live - `src/` — <what lives here> - `tests/` — <test conventions> - <add the files/specs you used to bundle into a Copilot Space> ## Conventions Claude must follow - Code-first: prefer showing edited code/diffs over prose explanations. - Keep responses concise. - Match existing style, lint, and test patterns; run the test suite before declaring done. ## How to work in this repo - Use Plan mode for multi-file tasks; surface the plan before editing. - Stage changes as diffs for review; don't auto-commit unless asked. - @-mention specific files/line ranges when you need targeted context. ## Reference docs / specs - <link or path to spec 1> - <link or path to spec 2>
Same-day walkthrough
This sample was built for an example user. Yours gets built around how you work.
A 15–25 minute interview captures your workflows, then the guide is generated for you — same structure, your prompts, your projects, your gotchas. Nothing in your stack is changed or cancelled by any of it.