Understanding GitHub Codespaces

PhantomWP uses GitHub Codespaces to provide you with a powerful development environment right in your browser. This guide explains what Codespaces are and how they behave.

What is a GitHub Codespace?

Think of a GitHub Codespace as a remote computer in the cloud that's specifically set up for your project. Just like your laptop has:

• An operating system (macOS, Windows, Linux)
• Storage for files
• RAM for running applications
• A CPU for processing

A Codespace has all of these too—except it runs on GitHub's servers instead of your desk.

Why Use a Codespace?

• No Setup - All tools pre-installed and configured
• Access Anywhere - Use from any browser, any device
• Consistent - Same environment for everyone
• Powerful - More resources than many laptops

Codespace Lifecycle

A Codespace can be in three main states, similar to how your computer can be running, asleep, or completely shut down.

When a Codespace Stops (Turns Off)

A Codespace stops automatically after a period of inactivity (usually 30 minutes). This is like putting your computer to sleep mode.

Computer Analogy: Sleep Mode

When your laptop goes to sleep:

• The screen turns off
• It stops using much power
• Your files and open programs are preserved
• When you open the lid, everything is exactly where you left it

A stopped Codespace works the same way:

Why Does It Stop?

GitHub stops inactive Codespaces to:

• Save resources — No point running a computer nobody's using
• Reduce costs — GitHub provides free hours each month
• Be eco-friendly — Less energy consumption

When a Codespace is Deleted (Destroyed)

This is different and more serious. When a Codespace is deleted, it's gone forever—like formatting your computer's hard drive.

Computer Analogy: Factory Reset

When you factory reset or format your computer:

• All files are permanently erased
• All installed programs are removed
• It's like getting a brand new computer
• You cannot undo this

When Does Deletion Happen?

Codespaces are automatically deleted after 30 days of inactivity. This means:

How PhantomWP Protects Your Work

Here's the good news: your code is safe in GitHub!

What Happens If Your Codespace is Deleted?

1. PhantomWP creates a new Codespace automatically when you open your project
2. Your code is pulled from GitHub into the new Codespace
3. Dependencies are installed automatically
4. You continue working as if nothing happened

The only thing you might lose is uncommitted changes—so commit often!

Comparison

Codespace Running (like computer on)

• Files safe: Yes
• Recovery time: Instant

Codespace Stopped (like computer asleep)

• Files safe: Yes
• Recovery time: 30-60 seconds

Codespace Deleted (like factory reset)

• Files safe: Only if committed to GitHub
• Recovery time: 2-3 minutes

Best Practices

To never lose work:

1. Commit frequently — Use the Git panel to save your work to GitHub
2. Push before closing — Make sure changes are uploaded
3. Use meaningful commit messages — Makes it easy to track changes
4. Don't worry about stopping — It's automatic and safe

Summary

• Codespace - A virtual development computer (like a computer in the cloud)
• Running - Active and working (like computer turned on)
• Stopped - Paused, all files saved (like computer in sleep mode)
• Deleted - Completely removed (like factory reset)
• Repository - Permanent code storage (like an external hard drive backup)

Next Steps

• IDE Overview — Learn how to use the PhantomWP editor
• Git Integration — Learn how to commit and push changes