GitHub Codespaces Problems & Issues
Real user-reported problems, complaints, and limitations for GitHub Codespaces. Based on analysis of 10 signals.
Issues by Category
Confusing billing system
The updated billing system is confusing to understand. Users struggle to see how much Codespaces time is available, how much has been used, and what charges apply. The earlier billing was much simpler with easy visibility of credits and usage.
Billing issues block free tier access
Some users are denied access to Codespaces despite being within the free tier because they have insufficient balance to cover other GitHub charges. Resolving this requires hours of support contact.
Storage costs continue even when suspended
Storage is billed for the entire duration the Codespace exists, regardless of whether it's active or suspended. Users expecting compute-only billing discover storage charges accumulating for idle environments.
Severe service outages with high error rates
October 2025 saw major Codespaces outages. On Oct 20, codespace creation averaged 39.5% error rate peaking at 71%, resume operations averaged 23.4% peaking at 46%. On Oct 29, connection error rates averaged 90% and peaked at 100%. These outages severely impacted developer productivity.
Remote host crashes during Copilot sessions
Users report remote host crashes occurring more frequently, especially during longer GitHub Copilot sessions. Crashes reset sessions and make progress impossible. The instability is particularly frustrating when working on complex tasks.
Commit functionality issues - infinite loading
Users report problems with committing changes in Codespaces where commit operations result in an infinite loading loop. This critical workflow disruption requires workarounds or switching to local Git operations.
Setup delays - stuck on 'Setting up your codespace'
Users experience Codespaces getting stuck on the 'Setting up your codespace' screen for extended periods. This startup delay defeats the purpose of instant development environments and wastes developer time.
Occasional slowdowns and performance issues
Performance issues are noticed by users with occasional slowdowns, often due to resource constraints or temporary service issues. Cloud-based development inherently adds latency compared to local development.
Only works with GitHub - no GitLab/Bitbucket
GitHub Codespaces only works with GitHub repositories. Teams using GitLab or Bitbucket are completely excluded. This vendor lock-in is a significant limitation compared to Gitpod which supports all three platforms.
RoguePilot security vulnerability exposed tokens
A RoguePilot flaw in GitHub Codespaces enabled Copilot to leak GITHUB_TOKEN. The vulnerability potentially allowed bad actors to seize control of repositories by injecting malicious Copilot instructions. Security-conscious organizations should be aware.
Regret Patterns
Common reasons users regret choosing GitHub Codespaces.
Outage during critical deadline
Teams discover the hard way that cloud IDEs can have outages at the worst times. October 2025's 100% error rates left developers unable to work during critical project phases.
Free hours exhausted mid-month
Active developers exhaust the 120 free hours faster than expected. The billing kicks in unexpectedly, especially confusing given the complex billing system changes.
Needed GitLab/Bitbucket support
Teams invested in Codespaces workflows discover they need to work with GitLab or Bitbucket repositories. The GitHub-only limitation forces migration to Gitpod or local development.
Storage costs accumulated while idle
Users discover storage is billed even when Codespaces are suspended. Forgetting to delete unused environments leads to unexpected charges month after month.
Remote host crashes lost work
Users experience remote host crashes during long coding sessions, especially with Copilot. Unsaved work is lost and session state resets, requiring restart of complex tasks.
Billing issues blocked free tier access
Users within free tier limits get blocked due to unrelated billing issues on their GitHub account. Resolving requires hours of support contact, wasting valuable time.
When GitHub Codespaces Breaks Down
Specific scenarios where GitHub Codespaces fails or underperforms.
Service outage during active development
When GitHub Codespaces experiences outages (like October 2025's 100% error rates), development completely stops. No offline fallback exists. Teams without local development backup are paralyzed.
Project requires GitLab/Bitbucket
GitHub Codespaces cannot connect to GitLab or Bitbucket repositories. When projects require non-GitHub repos, Codespaces becomes useless and teams must migrate to Gitpod or local development.
Heavy usage exhausts free tier
Active development quickly exhausts 120 free core hours. Without monitoring, unexpected billing kicks in. The confusing new billing system makes understanding charges difficult.
Long Copilot session crashes
Extended sessions with GitHub Copilot frequently cause remote host crashes. Work is lost, sessions reset, and complex in-progress tasks must be restarted. Productivity suffers significantly.
Security audit reveals cloud IDE risks
Security reviews flag vulnerabilities like RoguePilot. Organizations with strict requirements may need to abandon cloud IDEs or implement additional security measures.
Internet connectivity becomes unreliable
Codespaces requires constant internet. Travel, ISP issues, or working from areas with poor connectivity means zero productivity. No offline mode is available.