GitHub Copilot Faces User Backlash Over Rate Limit Changes
Severity: Medium (Score: 54.0)
Sources: Theregister, github.blog, stratoatlas.com, github.com
Summary
In April 2026, GitHub Copilot announced new rate limits following the discovery of a token counting bug that misrepresented usage costs. This bug led to a significant increase in user complaints as the limits imposed caused interruptions in workflows, with some users experiencing lockouts of up to 181 hours. GitHub's response included retiring the Opus 4.6 Fast model and recommending users switch to Auto mode, which selects lower-cost models but at the expense of performance. Users reported dissatisfaction with the abrupt changes, citing that the service they paid for was no longer reliable. The situation has led to a revolt among customers, with many expressing frustration over the lack of transparency and the impact on their coding tasks. GitHub's measures are seen as temporary fixes rather than solutions to the underlying pricing and execution contract mismatches. The overall sentiment among users is one of discontent and confusion regarding the service's reliability. Key Points: • GitHub Copilot's rate limits have caused significant user disruptions, with lockouts up to 181 hours. • A token counting bug revealed a mismatch between subscription pricing and actual usage costs. • Users are dissatisfied with the forced switch to Auto mode, which negatively impacts performance.