Skip to content
Discussion options

You must be logged in to vote

Hey! Yeah, Codespaces can burn through core hours pretty quickly if you’re not careful 😅

For idle timeout, I’d recommend setting it to around 15–30 minutes. That way it automatically stops when you forget about it, but doesn’t interrupt you too aggressively while working.

Also, quick clarification:

  • If a codespace is stopped, it does NOT use core hours
  • BUT it still counts toward your storage quota

So if you’ve got a bunch of old codespaces sitting around, they can eat up storage even if they’re not running.

What I usually do:

  • Manually stop it when I’m done
  • Delete old/unused codespaces regularly
  • Stick to smaller machine types unless I really need more power

That combo helps a lot in str…

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by denggs434
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug GitHub or a GitHub feature is not working as intended Codespaces Your development environment, in the cloud. Run VS Code and code on GitHub's cloud platform, source:ui Discussions created via Community GitHub templates
2 participants