Fix Bugs While You Sleep — Let Your Agent Run GitHub Copilot

I found a bug in my app. Numbered lists weren't rendering correctly in one of the views. Instead of opening my IDE, I sent my agent a message:

Can you implement something for me and open a PR in GitHub using Copilot? In my repo I want this: numbered lists don't seem to render nicely in view mode.

A few minutes later, there was a new issue on GitHub, Copilot was assigned, and a pull request appeared with the fix. I reviewed it, merged it, done.

Later that week, I noticed another bug — an input field not clearing after submission. Same thing:

Noticed a bug. Can you tell GitHub Copilot to open a PR with a fix for this: When sending a response using the human input tools, the input I wrote was still there when the agent asked me another question. We need to remove the input after sending.

Issue created, Copilot assigned, PR opened. Two bugs fixed without touching my editor.

How it works

GitHub has an official MCP server that exposes tools for managing issues, pull requests, repositories, and assigning GitHub Copilot's coding agent to work on issues. When you connect this MCP server to your agent in The Agency, your agent gets access to all of these tools.

The flow looks like this:

1. You describe the bug or feature to your agent
2. Your agent creates a GitHub issue with a clear description
3. Your agent assigns Copilot to the issue
4. Copilot reads the code, implements a fix, and opens a PR
5. You review and merge

You're describing problems in plain English. Your agent translates that into structured GitHub issues. Copilot writes the code.

Setting it up

The Agency already has a built-in GitHub app you can connect in Settings. It covers issues, PRs, code search, and more. But Copilot's coding agent is only available through GitHub's official MCP server, so to assign Copilot to issues, you'll need to add it as a custom MCP. This requires the Elite tier.

Here's how to set it up:

1. Create a GitHub Personal Access Token

Go to github.com/settings/tokens and create a fine-grained token with access to the repos you want your agent to work with. It needs permissions for issues, pull requests, and contents.

2. Add the MCP server

In The Agency, go to Settings → MCPs and add a new server:

• Name: GitHub
• Description: GitHub repository management and Copilot coding agent
• URL: https://api.githubcopilot.com/mcp/
• Authorization Header: Bearer your-token-here
• Custom Headers: X-MCP-Toolsets: all

The custom header X-MCP-Toolsets: all gives your agent access to all GitHub tools, including project management. Copilot works without it, but the extra tools are worth having.

Hit "Test Connection" to verify it works. You should see a tool count confirming the connection.

3. Start using it

That's it. Your agent now has access to GitHub tools. Try something like:

Create an issue in my-org/my-repo about the login button being misaligned on mobile. Assign Copilot to fix it.

Your agent will create the issue, assign Copilot, and Copilot will open a PR with a fix.

Tips for good results

The quality of Copilot's fix depends on how well the issue describes the problem. Your agent is good at turning vague descriptions into clear issues, but you can help:

• Be specific about where. Mention the file, component, or page where the bug occurs.
• Describe what happens vs. what should happen. "The list renders as bullets" vs. "it should render as numbered items."
• Mention the repo if you have multiple. "In the my-app repo."

You can also ask your agent to check on progress:

What's the status of the PR Copilot opened for the numbered list fix?

What else can you do with GitHub tools?

Beyond Copilot, your agent can now:

• Triage issues. "Summarize all open issues in my-repo and label them by priority."
• Review PRs. "What changed in PR #42? Give me a summary."
• Manage project boards. "Move the login fix issue to the Done column in my project board."
• Monitor CI. "Did the latest build pass on main?"
• Search code. "Find where the authentication middleware is defined in my-repo."

The GitHub MCP server gives your agent full read and write access to your repositories, limited only by the permissions on your token.

The bigger picture

This is what happens when AI agents can talk to each other. Your agent in The Agency understands what you want. GitHub Copilot understands how to write code. Connect them, and you can go from "I noticed a bug" to "here's a PR with the fix" without switching out of your chat.