What Copilot Workspace does
Copilot Workspace takes a GitHub issue or a task description and produces a full implementation plan: which files to create or modify, what changes to make, and why. You review and edit the plan before any code is written, which is fundamentally different from Copilot's inline completions.
Workspace understands your repository's existing patterns. It reads relevant files, follows your naming conventions, and writes code that fits your codebase rather than generic examples. The output quality is proportional to how well your existing code is structured.
Start from a GitHub issue
Open any GitHub issue in your repository and click 'Open in Workspace'. Copilot reads the issue description, scans related files, and generates a plan. The plan lists specific files to create or edit with a description of what each change does.
Review the plan before proceeding. You can edit the plan — add steps, remove steps, or change the description of individual changes. The more specific you make the plan, the more accurate the implementation. Vague plans produce vague code.
Write an effective task description
When starting from a text promptPromptThe input text sent to a language model — the question, instruction, or context that triggers a response.Learn more → (not an issue), be specific about inputs, outputs, and constraints. Instead of 'Add search to the blog', write 'Add a full-text search endpoint GET /api/posts/search?q= that searches the title and body fields using a case-insensitive substring match. Return the same JSON structure as GET /api/posts.'
Reference existing files or functions when relevant: 'Follow the pattern in src/handlers/posts.ts when creating the search handler.' Workspace will read that file and mirror its structure.
Review and iterate on the implementation
After Workspace generates code, run it in the built-in terminal. If tests fail or the output is wrong, describe the issue in the Workspace chat: 'The search is case-sensitive. Fix it to be case-insensitive.' Workspace will revise the implementation.
Workspace sessions can be shared via URL — useful for code review or for handing off a task. All changes are on a branch; you create a pull request from the Workspace UI when satisfied.