GitHub Copilot now lets you review code changes, run tests, and preview results without leaving the app.
Previously, checking an agent’s work required jumping between your editor, a terminal window, and a web browser. These tasks now live in built-in panels within the Copilot app, keeping your workflow contained.
Reviewing changes with the diff panel
The diff panel displays exactly what lines were added, removed, or altered. Additions appear in green and deletions in red.
This clarity allows you to accept modifications, leave comments, or request further edits from Copilot. You retain full control over the final output.
Executing commands in the terminal panel
Reading code is one thing, but running it is another. You can execute commands directly inside the Copilot app’s terminal panel.
Most actions involve running the project’s standard commands and reading the output. You can type these manually or configure them as scripts using the Run button.
Consider a website project as an example:
- Add a
dev serverscript that opens the client folder and executesnpm run dev. - Click Run to launch the server.
You can keep multiple terminal windows open to switch between them and manage concurrent commands.
Testing features with the browser panel
For projects with a user interface, the browser panel completes the workflow. Using the website example, this panel lets you open the site and test your new feature as if you were a visitor.
To refine the work, you can use the Pick & Polish tool. This lets you select an element and ask the agent to adjust it.
After making changes, run the dev server script again to see the updated results.
Finalising the review loop
Once you have reviewed the diff, started the project in the terminal, and verified it in the browser, you can accept the change directly from the app to create a pull request.
Handling the entire loop in one place eliminates the need to switch tabs or applications. Having review, execution, and preview side by side makes agent-generated changes feel safer because you can verify they function correctly before merging.
What it means
These built-in panels address three essential questions you should ask before accepting any automated work:
- What has changed?
- Does it run?
- Does it actually work?
Running through this checklist ensures you understand the modifications and confirm the code behaves as intended, keeping you in charge of the final product.
