FrogPilot Rebuild

FrogsGoMoo · Creator of FrogPilot
On this page

I went into both 2024 and 2025 with the exact same mindset, FrogPilot will be "done" by the end of the year. And both years the exact same thing happened. My skills improved and my definition of "done" moved right along with them, and I got stuck in a never ending loop of reworking code and improving features, chasing a finish line that kept walking away from me.

So this time I'm doing it differently, and honestly, way simpler. Instead of staring at the full completed picture and endlessly polishing it, I'm starting from a completely fresh version of stock openpilot and rebuilding FrogPilot from scratch, one piece at a time. Every single piece gets my full, undivided attention before I move on to the next one.

To pull that off, I'm using "Claude", "Codex", and "Gemini" in unison to absolutely tear my code apart. Their whole job is to find any and every issue they can, dig up improvements to the features themselves, and essentially call me an idiot as many times as it takes until every piece truly is "done".

To be crystal clear though, I'm not "vibecoding" FrogPilot. The AI isn't writing FrogPilot for me. It's there to enhance my workflow and rip apart my code to find flaws in it, and everything it flags gets manually reviewed and reworked by me. Nothing about how much you can trust FrogPilot changes, the code just gets way more eyes on it than I could ever manage alone.

How the rebuild works

#

The process is dead simple, one piece at a time. I pick a feature, rebuild it from the ground up, and then it goes through my vetting process where it gets torn apart, refined, and perfected until I'm fully confident in it. Nothing gets rushed, and nothing gets a pass just because it "mostly works".

Once a piece makes it through all of that, it lands on the "FrogPilot-Testing" branch. So by the time a feature shows up there, it's not just ready to be tested, I already consider it production ready!

On top of that, the 1st Saturday after every official openpilot release, a "snapshot" of the latest stable FrogPilot build gets pushed to the "FrogPilot-Staging" branch. So if you just want to enjoy the latest version of FrogPilot with fewer rough edges, "FrogPilot-Staging" is the branch for you!

And once the rebuild is fully complete, the "FrogPilot" branch itself joins the same rhythm, getting updated the 1st Saturday after every official openpilot release.

ETA?

#

Yes.

In all seriousness, the ETA is anywhere from tomorrow to December 31st, 2099. I am not rushing this to meet some arbitrary deadline. After two years of chasing "done", the only goal that matters is making sure this is done properly the first time.

Disclaimer

#

Just because something passes my vetting process doesn't mean it's 100% stable. Nothing is perfect, edge cases get missed, and at the end of the day I'm just one guy doing this in my extremely minimal amount of free time. So if you run into an issue, you NEED to report it in the "staging-bug-reports" channel in the Discord. I can't fix what I don't know about!

Just be fully aware of what you're signing up for. "FrogPilot-Testing" is considered the "Alpha" and "FrogPilot-Staging" is the "Beta". If you'd rather not run into any issues at all, you're better off waiting for the update to hit the "FrogPilot" branch once everything is fully completed and done.

What's been added back so far

#

Here's everything that's made it through the process so far. This list gets updated as pieces land, so check back often!

High priority

#

These are at the top of my shortlist and what I'm focusing on next.

Rough list of what's still missing

#

And here's a rough idea of what's still waiting its turn. Fair warning though, this list is VERY incomplete. FrogPilot has over 200 features, so the chances of me missing one or two here are pretty much a guarantee. The "What's been added back so far" list above is the source of truth, so if something isn't on that list, it's not back yet.