My codespace locked due to reaching full limit of the free tier.

[ItzJatinOG]

Select Topic Area

Question

Body

My codespace locked due to reaching full limit of the free tier. i have my work unpushed to it and now I am trying the export to brach method but it failing everytime I try. pls give me solution about that.

[Synalix]

The GitHub Free tier provides 60 hours of usage per month. If you have hit your limit, the easiest (though slowest) fix is waiting for your monthly quota to reset.

Check your reset date: Go to your GitHub Settings > Billing and plans > Plans and usage.

Scroll down to Codespaces to see when your monthly hours refresh.

If you can’t wait for the reset, you can enable a small amount of "Paid Usage" to unlock the Codespace for just a few minutes i guess

[ItzJatinOG]

Thanks for the suggestion. Unfortunately, I can’t really wait for the reset because my usage resets in about 17 days, which is a long time for my project. I also can’t enable paid usage since I’m under 18 and don’t have a credit card or a PayPal account, so I’m limited to the free tier only. If anyone knows another workaround or alternative, I’d really appreciate the help.

[Synalix]

If the Codespace won’t start, there’s no way to access its filesystem at all. GitHub doesn’t let you mount or copy the files while it’s powered off due to hitting the free-tier limit. The “export to branch” method basically needs the Codespace running to commit and push changes, so that’s why it’s failing.Without starting it, there’s no official way to download or copy the project locally. You could perhaps contact Github's support but I doubt they can help you with this. Most likely you will have to wait until your cooldown resets.

[DeveloperVaibhav1]

If your Codespace is locked due to the free-tier limit, one thing you can still try is checking whether the repository contains any autosaved commits or checkpoints.

Sometimes Codespaces automatically keeps changes in the workspace even if they were not pushed yet. You can try:

1. Opening the repository on GitHub.
2. Go to the Codespaces tab for the repo.
3. See if there is an option like Download workspace or Export changes.

Another thing you can try is opening the repo locally and checking whether any work was already synced:

bash
git fetch origin
git log --all

Occasionally the Codespace may have created temporary commits that are not on the default branch.

If none of these options work, the only guaranteed solutions are:

• Wait for the monthly Codespaces quota reset, or
• Temporarily enable paid usage to start the Codespace for a few minutes, commit the work, and push it to the repository.

For future projects, it’s a good idea to push changes frequently or commit to a branch regularly to avoid losing work if a Codespace stops due to quota limits.

[AakashSingh07]

If your Codespace is locked due to the free-tier limit, your data is usually still preserved in the environment.

If you can briefly unlock it (for example by enabling a small amount of paid usage), you could quickly push your changes to the repository using:

git add .
git commit -m "save work"
git push

Another option is to export or download the Codespace content from the repository page or reopen the environment locally using GitHub CLI if available.

Unfortunately, when the free-tier hours are exhausted the environment itself becomes restricted until the quota resets, so temporarily enabling paid usage for a few minutes is often the fastest way to recover the work.

[DeveloperVaibhav1]

If your Codespace is locked because you reached the free-tier limit, the environment usually cannot start until the usage resets or billing is enabled. However, your files are still stored in the Codespace storage.

You can try these options:

1. Go to Repository → Code → Codespaces and open the … (three dots) menu of the locked Codespace.
   Click “Export changes to branch.” Sometimes it fails due to a timeout, so try refreshing the page and running it again.

2. If it still fails, try enabling billing temporarily, start the Codespace, commit your changes, push them to the repository, and then stop or delete the Codespace.

3. Otherwise, you may need to wait until the monthly free-tier usage resets, then start the Codespace and push your work normally.

These are usually the available ways to recover unpushed work from a locked Codespace.