GitHub Copilot Workspace for Issue-Driven Development Walkthrough

GitHub Copilot Workspace is a new browser-based development environment that connects directly to your GitHub issues. Instead of switching between your issue tracker, local IDE, and documentation, you can read the issue, plan a fix, write code, and test changes all inside one Copilot-powered interface. This walkthrough explains how to use Copilot Workspace for issue-driven development, from selecting an issue to reviewing the generated pull request.

The core idea behind Copilot Workspace is to reduce the friction between identifying a problem and delivering a solution. It uses the context from your repository, the issue description, and the conversation history to suggest a concrete plan and code changes. This is especially useful for developers who want to fix bugs or add features without manually parsing the entire codebase first.

This article covers the complete workflow: opening Copilot Workspace, interpreting an issue, refining the AI-generated plan, applying code changes, and creating a pull request. You will also learn how to handle incomplete or ambiguous issues, and how to review the changes before committing them.

What Is GitHub Copilot Workspace and How Does It Work

Copilot Workspace is a Copilot-powered development environment that runs entirely in the browser. It integrates with GitHub issues, pull requests, and repository contents. When you open an issue in Workspace, the system reads the issue title, description, comments, and labels. It also fetches the relevant files from your repository, including the code, configuration, and documentation.

The environment uses the GPT-4 model fine-tuned on code and software engineering tasks. It generates a plan of action that describes what files to modify and how. You can edit the plan, add or remove steps, and ask clarifying questions before the system writes any code. After you approve the plan, Copilot Workspace produces a set of code changes shown as a diff. You can review each change, edit it inline, and finally create a pull request from the workspace.

Prerequisites for Using Copilot Workspace

To use Copilot Workspace, you need a GitHub account with an active Copilot subscription. Copilot Workspace is available to Copilot Enterprise, Copilot Business, and Copilot Individual subscribers. The repository must be public or private with Copilot access enabled. No local installation is required because everything runs in the browser.

Steps to Use Copilot Workspace for Issue-Driven Development

This section walks through the complete workflow from opening an issue to creating a pull request. All steps are performed in the browser.

1. Open the issue in your repository
   Navigate to the repository on GitHub.com. Click the Issues tab and select the issue you want to work on. The issue should have a clear title and description. If the issue is missing context, add comments or labels to help Copilot understand the scope.
2. Click the Open in Workspace button
   On the issue page, locate the Open in Workspace button. It appears near the top right of the issue body, next to the Assignees and Labels sections. Clicking this button opens a new browser tab with Copilot Workspace loaded for that specific issue.
3. Review the generated plan on the Plan tab
   Copilot Workspace displays a plan in the Plan tab. The plan lists the files that need changes, the type of change for each file, and a summary of the logic. Read each step carefully. If the plan is incorrect or incomplete, click the Edit button below the plan. You can add new steps, reorder them, or delete irrelevant ones.
4. Ask clarifying questions if needed
   Below the plan, there is a chat input field. You can type questions such as: Why is this change needed in the auth module? or Should we also update the test file?. Copilot responds with explanations and may update the plan automatically based on your feedback.
5. Approve the plan to generate code changes
   When you are satisfied with the plan, click the Approve and Generate Code button. Copilot Workspace creates the code changes and shows them in the Code tab. Each modified file appears with a side-by-side diff view. The left side shows the original file, and the right side shows the proposed version.
6. Review and edit code changes inline
   In the Code tab, you can click any line in the diff to edit it directly. You can add new lines, delete lines, or modify the Copilot-generated code. The environment validates syntax for supported languages, but it does not run tests automatically at this stage.
7. Create a pull request from the workspace
   After reviewing and editing the changes, click the Create Pull Request button. Copilot Workspace creates a new pull request in your repository. The pull request includes the issue reference in the title and description. The branch name is generated automatically based on the issue number and title.

Common Issues and Things to Avoid

Copilot Workspace is powerful, but it has limitations. Understanding these will help you avoid wasted time and incorrect changes.

Copilot Workspace generates an incomplete plan

If the issue description is vague, the generated plan may skip important steps. For example, an issue that says Fix login error without a stack trace or reproduction steps will produce a generic plan. To fix this, edit the issue before opening it in Workspace. Add specific error messages, expected behavior, and affected files. You can also use the chat input in Workspace to ask Copilot to re-analyze the issue with more context.

Code changes do not compile or fail tests

Copilot Workspace generates code based on the repository snapshot and issue context. It does not run your test suite or build system. After creating the pull request, your CI pipeline will run tests as usual. If tests fail, edit the changes directly in the pull request branch using the GitHub web editor or your local IDE. You can also return to Copilot Workspace, adjust the plan, and regenerate the code for the same issue.

Copilot Workspace modifies files outside the issue scope

Sometimes the AI suggests changes to files that are not directly related to the issue. This can happen if the issue description mentions a broad concept. To prevent this, review the plan carefully and remove any step that modifies files you do not want to change. In the Plan tab, click the X button next to a step to delete it. You can also add explicit constraints in the chat, such as Only modify files in the src/controllers directory.

Item	Copilot Workspace	Traditional Local IDE Workflow
Setup required	None beyond browser and GitHub login	Clone repo, install dependencies, configure IDE
Context gathering	Automatic from issue, repo, and comments	Manual reading of issue, code, and docs
Plan generation	AI-generated plan with editable steps	Developer creates mental or written plan
Code generation	AI writes code after plan approval	Developer writes code manually
Pull request creation	One-click from workspace	Manual git commands or IDE plugin

Copilot Workspace is not a replacement for your local development environment. It is best used for quick fixes, small features, and well-defined bugs. For large refactors or complex architecture changes, you should still use your local IDE with Copilot for code suggestions.

After you create a pull request from Copilot Workspace, you can continue working on it locally. The branch created by Workspace is a standard Git branch. You can pull it to your local machine, make additional changes, and push updates. The Workspace session remains available for reference until you close it.

For teams, Copilot Workspace helps standardize the way issues are resolved. Every change is linked to an issue, and the plan provides a clear record of the intended approach. This makes code reviews easier because reviewers can see both the plan and the resulting diff in the pull request.