GitHub ended the Copilot Workspace technical preview on May 30, 2025. The preview showed how a developer could turn a GitHub issue into a plan, review the proposed code and open a pull request. If you need a workflow you can use today, compare GitHub Copilot’s editor and cloud options.
What Copilot Workspace Actually Is
Copilot Workspace was a browser-based development preview for GitHub repositories. A GitHub issue could start a session, and the developer could edit the plan before asking Workspace to generate code. The stages below describe that retired preview.
The Issue-to-PR Workflow
Start from an issue. Workspace used the issue and repository context to summarize the requested change.
Review the plan. The developer could change the proposed steps and which files would be affected before any code was generated.
Inspect the changes. Workspace proposed edits across the files in the plan. The developer could read the diff, the list of changes to the code, and revise the work.
Open a pull request. A pull request asked other people to review the change before it entered the project. Workspace could open one from the session after the developer reviewed the work.
Natural Language Planning Done Right
A plan gave the developer something concrete to review before any code was written. It described which files needed changes and which new files might be needed. The developer could edit, add, remove or reorder steps before generating code.
Multi-File Code Generation
The preview could propose changes across several files after the developer agreed on the plan. A change could affect an application file, the code that calls it and its tests. The developer could inspect and revise each edit before opening a pull request.
GitHub Ecosystem Integration
Starting from a GitHub issue kept the request near the repository and the proposed changes. The useful habit is to keep enough of the plan with the pull request for someone else to review the reason for the edit and see which checks were run.
How It Differs from Copilot Chat and Agent Mode
Workspace organized its preview around an issue, an editable plan and a pull request. A chat explanation and an editor session have different starting points. If you use an agent for a similar task today, check where the agent will run, which files it can access and who will review the result.
Limitations Worth Knowing
The plan could only work with the context it had. Authentication patterns, deployment requirements and business rules known to the team might be missing from the repository. State those constraints in the issue and check that the proposed edits respect them.
Who Should Actually Use This
The preview is retired. Its review sequence is still useful when a task spans several files. Agree on the expected behavior, check the proposed plan, inspect the changes and ask a person to review the pull request.