Error Assigning Copilot via API: "The agent encountered an error and was unable to start working on this issue: This may be caused by a repository ruleset violation"

[danmcpherson]

Select Topic Area

Bug

Body

Starting today, we are seeing the following error in timelines whenever we are assigning Copilot to work on an issue using the API:

"The agent encountered an error and was unable to start working on this issue: This may be caused by a repository ruleset violation. See granting bypass permissions for the agent, or please contact support if the issue persists."

We can assign Copilot via the Web UI with no issue. There are NO rulesets on the Repo or at the Org level.

Reproduction Steps

POST https://api.github.com/repos///issues/<issue#>/assignees
Body: {
"assignees": [
"copilot-swe-agent[bot]"
],
"agent_assignment": {
"working_branch_prefix": "copilot/issue-#",
"model": "claude-opus-4.6"
}
}

This returns:
Status: 201 Created
✅ Copilot assigned successfully!
Assignees: Copilot,

However, the above error quickly displays in the timeline.

For testing:
We use an account that is part of the Organisation, and is an Admin on the Repo.
We are using a PAT that has the right permissions, and we have tried different accounts (all which were working).

Anyone else seeing this?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[scholtz]

i have the same issue on 3 different repos. started to occur something like 6-12 hours back

i have no rulesets on my repos

i use the copilot-cli to create issues, and assign it to copilot and then to merge it..

https://github.com/scholtz/events
https://github.com/scholtz/biatec-tokens
https://github.com/scholtz/biatectokensApi

now it gets stucked on creating issue and not assigning it to copilot. when i assign it manually through github ui it works

[scholtz]

Is there any recommended steps how to solve this issue?

I create github issues using gh issue create --title $title --body-file /tmp/issue.md --assignee copilot-swe-agent command

https://github.com/scholtz/events/blob/main/.github/agents/adam-product-owner.agent.md#create-github-issue

[danmcpherson]

I have tried:

1. GraphQL > Same issue.
2. GitHub CLI (the command you list) > Same Issue.
3. Claude third party bot > Same issue
4. We have tested on multiple Repos and Multiple Orgs > Same issue.
5. It does work from VS Code when you create a "Cloud" session (creates a PR assigned to Copilot)

What has also worked is to create a new PR, then @copilot on the PR. Copilot then creates a sub-PR, and works on the issue, but this is not the same thing, and less than ideal.

@scholtz have you raised a support ticket? mine is #4186226

[scholtz]

Mine is #4188339

[scholtz]

i did not get any reply so far.. did they write you something to the ticket?

[danmcpherson]

No, nothing. See my note below about oAuth working?

[scholtz]

how to authorize copilot to use oAuth?

[danmcpherson]

It looks like it's fixed.

[Dharmik2510]

Same issue for me

[Dharmik2510]

Let me know if you find any workaround :)

[vgithib]

Started seeing the same issue since last few days

[scholtz]

no solution yet, and its quite blocking.. have you created a support ticket? Perhaps if more people file this in tickets they will prioritize the fix. https://support.github.com/tickets/personal/0

[danmcpherson]

I have seen that it DOES work when using oAuth authentication. I found this out while testing with the GitHub Pull Request extension in VSCode which allows you to “Assign to Coring Agent”.

I'm using a "fine grained" PAT, and I've given it a full range of permissions (org and repo), but had the same result.

[allanmo79]

Same, suddenly happended any suggested solutions?

[scholtz]

no solution yet, and its quite blocking.. have you created a support ticket? Perhaps if more people file this in tickets they will prioritize the fix. https://support.github.com/tickets/personal/0

[introwit]

facing this exact same issue, did anyone find a workaround?

[scholtz]

no solution yet, and its quite blocking.. have you created a support ticket? Perhaps if more people file this in tickets they will prioritize the fix. https://support.github.com/tickets/personal/0

[introwit]

created the ticket 🤞🏽

[loflet]

The workaround which @danmcpherson mentioned about using OAuth instead of PAT worked for us. So if we use OAuth token then it works but if used PAT token then it doesn't.

[alextrep96]

Same here, started failing last friday and can't get it to work. I confirm I can assign task manually from Github but as soon as I try to do it from the gh api commands I get the same error as you. Looks like they added the OAuth restriction to the API as they did to the gh agent-task create (as described here)...

[danmcpherson]

It seems like it has started working again, will continue to test, but interested in any other feedback.

[MIKALAI-HURYN]

Yes, it works for me now as well.

[introwit]

yep, it now works for me too

[seehorne]

This functionality appears to be back online for me!
(Note: my use case was assigning via a Github action, which I believe implicitly calls the API, though I was not explicitly calling the API myself. I do think it was the same issue though, since all of the downtimes have matched)

[MIKALAI-HURYN]

Now I see a slightly different error:
The agent encountered an error and was unable to start working on this issue: Please try again later, or contact support if the problem persists.

[deb-adarsh]

I've put up a discussion for this - https://github.com/orgs/community/discussions/191654

[introwit]

it now replies with a different error message:

The agent encountered an error and was unable to start working on this issue: The service is temporarily unavailable. Please try again later.

[EBoiSha]

Same issue here, following the same steps:

The agent encountered an error and was unable to start working on this issue: The service is temporarily unavailable. Please try again later. (Request id: 80F2:1D4933:398B93:5E81D6:69CCE4E3)

[syedsafeer]

Hi @danmcpherson,
since you've confirmed there are no explicit rulesets, this is likely a permissions or metadata sync issue with the bot agent.
A few things to double-check:

1. Fine-grained PAT: Ensure your token has 'Read and Write' access to Issues, Pull Requests, and most importantly, 'Read' access to Metadata.
2. Copilot Org Policies: Check if your Organization has a policy that restricts 'Copilot for Extensions' or third-party agents from performing write actions.
3. Branch Protection: Even if 'Rulesets' are empty, check if there are any old-style Branch Protection Rules on the default branch that might be blocking the agent from creating a new branch.

If these settings are correct, it might be a temporary backend glitch with the Copilot API.

(Hope this helps! If it does, please feel free to Mark as Answer.)

[MIKALAI-HURYN]

API calls are working again for me.

[arnab-senapati]

Ah yes, the classic '201 Created but actually failed asynchronously'—definitely feels like a backend regression!

[romanws]

I'm getting:

The agent encountered an error and was unable to start working on this issue: The service is temporarily unavailable. Please try again later.

[jasonjoh]

I'm running into this same issue: "The agent encountered an error and was unable to start working on this issue: This may be caused by a repository ruleset violation."

For me, I'm using an app installation token. I started this with just Read/Write on Issues (and the mandatory Read on Metadata), but in trying to make this work, I've expanded so now I have:

• Actions: Read/Write
• Agent tasks: Read/Write
• Contents: Read/Write
• Issues: Read/Write
• Metadata: Read
• Pull requests: Read/Write

This is all happening in one of my personal repositories with no rulesets. I can assign to Copilot manually with no issue.

[jakemcallister]

Same issue for me - has anyone got a good workaround or had a response on any support tickets?

[Suman-jha-simform]

Getting this error while trying to assign task to copilot: " The agent encountered an error and was unable to start working on this issue: Please try again later, or contact support if the problem persists "

[Bhavin14199]

Started getting this error again: The agent encountered an error and was unable to start working on this issue: Please try again later, or contact support if the problem persists.

• has anyone got a good workaround or had a response on any support tickets?

[JoshGreenslade]

This has restarted for us as well - seeing it pretty much every time a PAT token is used to assign an issue to an agent. No workarounds that I know of so far

[vgithib]

One workaround which works is to use the Github Rest API instead of graphql for assigning issue to copilot:
https://docs.github.com/en/rest/agent-tasks/agent-tasks?apiVersion=2026-03-10#start-a-task

There are some caveats:

1. The issue will keep showing the "Assign to Agent" Button even if copilot has picked up the issue
2. Sessions related to the issue are not visible at issue header
3. Repeated assignment of an issue to copilot via Rest API creates new sessions and PRs, unlike graphql where reassigning same issue again mostly had no effect

[QlunkOllio]

Hi guys!
I ran into this issue today and found that when using Haiku 5.5 i got that error but when switching to another model (GTP 6 Luna) it worked.

[yanmariomenev]

I can also confirm that changing from Claude-Haiku-5.5 to a GPT model like "gpt-6.1-sol" fixes the issue. There needs to be a better error message for this.