GitHub Copilot app brings together in one place the steps for reviewing and running the changes an agent makes to code and viewing the results. This allows the AI-assisted coding process to be completed without switching between the editor, terminal, and web browser.
The Diff panel displays added, deleted, or modified lines in their previous and current forms. Additions are marked in green, while deleted sections are marked in red. Users can accept the changes, leave comments, or ask Copilot for further edits; the final decision remains with the user.
The Terminal panel allows project commands to be run directly within the session. Code can be started manually, and a script that can be run from the Run button can also be configured. For example, a development server script can be added to open the client folder for a website and then run the npm run dev command. Multiple terminal windows can be kept open at the same time.
Projects with user interfaces can be opened in the Browser panel, allowing new features to be tested under real-world conditions. With the Pick & Polish tool, an element can be selected and the agent can be asked to edit it; the development server can then be restarted to check the result.
Once the desired stage has been reached, the change can be accepted from within GitHub Copilot app and a pull request can be created. The process is intended to make it possible to see what has changed and verify whether the project works and performs the expected function.
Why it matters
This update makes the review process more traceable by bringing the handoffs between code generated by the AI agent and human oversight into the same workspace. Users who ask the agent to make edits can not only view line-by-line differences but also test in the same session whether the change allows the project to run and see its result in the user interface. Keeping the options to accept, comment, and request further edits in the user’s hands enables a staged control loop rather than turning automation directly into approval. Adding pull request creation to this workflow also reduces transitions between tools from code changes through validation; however, the need to configure terminal scripts and the reliance of browser testing on projects with user interfaces leave open the question of whether the same validation coverage can be achieved across different project types.
Background
GitHub is not a new name in the FikirPilot archive: over the past 90 days, we published 2 articles mentioning the name, the most recent on September 5, 2026.