Update a codebase with Copilot in chat and agent mode
A developer used GitHub Copilot to make code changes and preferred the CLI’s autopilot workflow and todo list.
- What they did
- A commenter said they use GitHub Copilot inside VS Code to handle codebase changes through chat and agent mode. In the thread, they asked how the CLI compares on premium-request handling and answer quality, and the reply said the CLI follows the same premium-request multiplier rules as the IDE. They also described the CLI agent as a system that examines the repository, lays out a plan, writes code, runs tests, and opens pull requests.
- How it went
- Their report was subjective rather than measured: they said the CLI gives better results for them and that they usually leave it in autopilot. No counts, timing data, or success rates were provided.
- Tips
- For this kind of task, ask for a plan first and make the agent wait before any irreversible action. If the work touches tests or build steps, tell it to pause whenever a decision or approval is needed.
Try it yourself with GitHub Copilot
Use GitHub Copilot CLI to help with [describe the change to my codebase]. Start by reviewing the repository and writing a short task list, then show it to me and wait for approval. After that, complete the items one at a time, marking each one off, and run the relevant tests or build checks along the way. Stop before any irreversible action, such as submitting, sending, deleting, or opening a pull request, and ask me to confirm first. When you finish, give me a brief summary of what changed and anything that still needs attention.
Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.
Get 3 agent uses like this every morning
With the day's top AI news. Free, and one click to unsubscribe.
Related agent uses
Use Copilot for narrow coding tasks only
A developer first let GitHub Copilot Agent Mode handle most coding, then restricted it after losing track of their own code.
Split development work into phases before using Copilot
A developer plans features in stages first, then feeds the approved steps to GitHub Copilot instead of asking it to make all architecture decisions at once.
Use Copilot for a tightly managed coding day
A commenter had GitHub Copilot produce all the code they pushed in one day, with close supervision throughout.
Use Copilot to draft a hard Flutter function
A developer had GitHub Copilot write a tricky Flutter function, then checked it with their own tests and harness.
Break a runtime migration into tiny reviewable PRs
GitHub engineers had Copilot agents carry out most of a large TypeScript-to-Rust runtime rewrite.
Run terminal commands carefully in Copilot agent mode
A VS Code user had Copilot agent mode run shell commands, but it often missed output or got stuck until they changed the shell setup.