zach.codes

zach.codes

Share this post

zach.codes
zach.codes
I Used GitHub Copilot+ For a Week

I Used GitHub Copilot+ For a Week

A very quick look at Copilot Agent and the ways I used it

Zach Silveira's avatar
Zach Silveira
Jul 03, 2025
∙ Paid
1

Share this post

zach.codes
zach.codes
I Used GitHub Copilot+ For a Week
Share

A few weeks ago when Copilot Pro+ was announced, I paid the $40 and started using it. I was super intrigued because having an AI agent on GitHub's website directly seemed like a pretty powerful tool.

It's not like there's a new model or anything, but the cool part is being able to have AI interact with pull requests and issues.

I think it helps a team level up if multiple people can go review a PR and have AI address it without you having to pull anything locally on your device (or into a codespace)

This leads us into our first big problem with Copilot’s Agent: currently, there's no way to have it respond to PR questions or comments that weren't originally started by Copilot.

It can do this, but only when it's the one who originally opened the pull request.

Real Examples

I'll go through and share some screenshots of some real results I did in the repository of mine. I used it so much during my testing that I got completely blocked and it started saying, "Unfortunately, I couldn't process your request." Through inspecting GitHub actions, I realized it's because I was rate limited.

Adding Sentry

I assigned it an issue that just said to add Sentry. Here’s what it added:

Keep reading with a 7-day free trial

Subscribe to zach.codes to keep reading this post and get 7 days of free access to the full post archives.

Already a paid subscriber? Sign in
© 2025 Zach Silveira
Privacy ∙ Terms ∙ Collection notice
Start writingGet the app
Substack is the home for great culture

Share