You can use github codespaces to bootstrap a piece of reproducible behaviour in a particular repository.

This is quite great for showcasing a piece of software. You can also run the software as if you’re running it locally without actually running it locally.

This includes GitHub copilot and other plugins.

I was more curious about GitHub Codespaces in general so I asked Claude Sonnet 3.5 that was within my Github Codespace how it all worked:

How It Works

When you create a codespace, GitHub: Spins up a container using your devcontainer.json configuration Sets up the development environment with specified tools and extensions Clones your repository into the container Connects it to VS Code (web or desktop)

“Code from anywhere with a browser”

Like for instance you can run, test and review code properly as you would from a pc/laptop.

“No local setup needed”

While this is technically true, but in practice, one would have to be well-versed with setup commands to make effective use of GitHub workspaces. Not an issue for the initiated.

Another major concern I had while learning about Codespaces was would the data be lost if code changes weren’t commited and pushed to remote source.

But looks like this concern was now relieved. The whole selling point of GitHub Codespaces was that a single codespace persists between sessions, meaning if you accidently close the tab “changes” can be restored.

However there are caveats!

If you’re personal account codespace wasn’t touched or used in last 30 days it will wipe the codespace clean.

While it’s a bummer, most of the workflows may not be hindered because almost everyone has a personal computer with them at most times. Codespace would mainly be used as a convenience layer to work out of a low computer hardware like a phone or tablets like Ipads.

Me personally, I like to make small commits and push to remote if it’s my personal projects. Also since this is remote, this is akin to having a VPS with OS and dependencies pre-installed for free to perform some cool experiments.

Moreover, it’s perfect for code-reviews.

All changes can be tested on a remote server without worrying about affecting your local server persistence or compute states.

Run a test, write a spec, edit typos, “quick fixes” and many more.

At least all of this can now be done without carrying your laptops to that park or cafe, if you have your tablets or iPads at your disposal.

Via Simon Willison’s TIL post on Configuring GitHub Codespaces

~ updated at: 2025-08-17T10:23:56.679Z