You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GitHub Copilot CLI started to time out when I did not immediately jump onto edit permission requests. I do leave sessions open over night, and I frequently have several sessions open in parallel, so these timeouts are really, really annoying. This only started happening with a recent update, I swear that this didn't occur in any session I had open a month ago, for example. Symptom:
✗ Edit Edit src/digestive.rs 10m 0s
● The edit did not apply because the permission request timed out; [...]
Affected version
/version says: ● GitHub Copilot CLI 1.0.80 You are running the latest version.
Steps to reproduce the behavior
Ask Copilot to make a code change. Let it wait for 10 minutes.
Expected behavior
Copilot should be as patient with me as I am with it.
Additional context
Seems to happen across OSes, I tested with WSL and with Windows. I'm using GPT 5.6 Sol, if that makes any difference.
Confirming. I think this should be a configurable timeout at the very least, so I can disable as I see fit. I also didn't see it before around one month ago.
If you go away-from-keyboard for a while, then it still consumes tokens because it retries. Meaning wasted AICs.
I also saw this on Linux (v1.0.75) and I hated it. At least on Linux (and I presume macOS) I could CTRL-Z suspend the CLI, but that just leads me to forget what I had running in that terminal.
It was a significant anti-feature.
With v1.0.87 on Linux, it seems to be resolved? Or at least the timeout is significantly longer than 10 minutes.
Thanks for the report. We've shipped fixes in this area since this was filed (most recently in Copilot CLI v1.0.83), and we believe this may now be resolved. Could you retest on the latest release (Copilot CLI v1.0.103) and let us know whether you still see it? If we don't hear back in a couple of weeks, we may close this issue — you can always reopen it.
Triaged as part of a Copilot SDK backlog review, with help from GitHub Copilot.
Activity
tchernobog commentedon Aug 27, 2026
Confirming. I think this should be a configurable timeout at the very least, so I can disable as I see fit. I also didn't see it before around one month ago.
If you go away-from-keyboard for a while, then it still consumes tokens because it retries. Meaning wasted AICs.
griffini commentedon Sep 22, 2026
I also saw this on Linux (v1.0.75) and I hated it. At least on Linux (and I presume macOS) I could CTRL-Z suspend the CLI, but that just leads me to forget what I had running in that terminal.
It was a significant anti-feature.
With v1.0.87 on Linux, it seems to be resolved? Or at least the timeout is significantly longer than 10 minutes.
patniko commentedon Oct 26, 2026
Thanks for the report. We've shipped fixes in this area since this was filed (most recently in Copilot CLI v1.0.83), and we believe this may now be resolved. Could you retest on the latest release (Copilot CLI v1.0.103) and let us know whether you still see it? If we don't hear back in a couple of weeks, we may close this issue — you can always reopen it.
Triaged as part of a Copilot SDK backlog review, with help from GitHub Copilot.