RepoRunner v0.1.3 is live. You can now save up to 5 local repo setups, switch between them from the setup screen, and keep using the same pull, install, start, stop, restart, preview, and logs workflow for the active repo. Still local-first. Still built for running repos without terminals. reporunnerapp.com

RepoRunner update: Read-only Analyze Repo is now merged. It inspects local scripts, lockfiles and project structure without executing anything. Next up: framework detection and evidence-backed setup suggestions. Still under review, but making good progress.

Been quietly making a bunch of small improvements to RepoRunner over the last little while. Nothing flashy, just polishing the experience and fixing the rough edges. A new version should be out soon.

GitHub manages your code. RepoRunner manages your local workspace. Organize your projects. Launch your repos. Jump between them in seconds. Less friction. More building 💪 reporunnerapp.com

We just submitted RepoRunner on @launch_llama! Check it out 🦙 tools.launchllama.co/product…

GitHub makes it easy to find repos. AI makes it easier to understand and edit code. But getting a repo running locally is still weirdly painful. That gap needs better tools.

The hardest part of trying a repo usually isn’t the code. It’s figuring out what the repo quietly assumes you already know.

A useful thing to check in any repo: .env.example If it exists, open it before running the app. It tells you what the project expects from the outside world: API keys database URLs auth secrets ports third-party services Missing env vars are one of the easiest ways to waste an hour.

Repo tip: Before cloning or running a repo, quickly check for: - package.json - .env.example - docker-compose.yml - README setup steps - database mentions - required Node/Python versions - frontend/backend folders Those files usually tell you how much setup friction you’re about to run into.

I don’t think every repo needs a perfect README. But every repo should make these things obvious: what it is what it needs how to install it how to configure it how to run it what URL to open The README doesn’t necessarily need to be long. It just needs to remove the guessing.

There are two types of GitHub repos: 1. Runs in 2 minutes 2. Makes you question your life choices RepoRunner helps with the latter.

What part of running local GitHub repos annoys you most? For me, it’s this repeat loop: pull latest install packages start frontend start backend open preview check logs stop/restart when something breaks None of it is hard. It’s just annoying to keep doing manually