This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
OB-1
Free coding agent. No account, no card, no API key.
OB-1 is an open-source coding agent for your terminal. Install it and start with no account, no card, no API key. Its free tier is a router built into the CLI that pools 162 free models across 22 providers, so no single vendor can pull the plug. After every change it runs your project's checks and fixes what broke until they pass. For frontier models, paid plans are prepaid credits, hard-capped, so no bill can run past the number you set. Install: brew install overbrilliant/tap/ob1
the auto-fix-until-tests-pass loop is the part I'd want to poke at. tests going green and the code actually being correct aren't the same thing - what stops it from taking the easier path when it's stuck, like weakening an assertion or patching the test itself instead of the real bug?
Tried it on a small script and the auto-fix loop actually caught a failing test on its own without me babysitting the terminal. The pooled free models are a nice touch too, no juggling API keys.
brew install was painless and the model router actually worked without me juggling keys. Loved that it ran my tests and kept patching until they passed.
Hey Product Hunt. I'm Tash. I built most part of OB-1 using OB-1, the product I'm launching here.
The free tier is genuinely free and stays that way, because the free models router is built into the CLI now: it pools the free tiers of 22 cloud providers (162 models right now), a few of them keyless so your first message needs no key or account, and you can drop your own free API keys into one file to unlock the rest for prototyping and trying out models. Do that. This lets you understand what models to use.
That model traffic goes from your machine to the providers, not through the server, so there's nothing for us to meter. If you want hosted frontier models on one bill, that's the paid tier.
OB-1 has fusion and best of N modes, that will help you solve complex problems. I'm keen to see what you build with it.
About OB-1 on Product Hunt
“Free coding agent. No account, no card, no API key.”
OB-1 was submitted on Product Hunt and earned 15 upvotes and 7 comments, placing #35 on the daily leaderboard. OB-1 is an open-source coding agent for your terminal. Install it and start with no account, no card, no API key. Its free tier is a router built into the CLI that pools 162 free models across 22 providers, so no single vendor can pull the plug. After every change it runs your project's checks and fixes what broke until they pass. For frontier models, paid plans are prepaid credits, hard-capped, so no bill can run past the number you set. Install: brew install overbrilliant/tap/ob1
OB-1 was featured in Software Engineering (42.7k followers), Developer Tools (515.5k followers) and Maker Tools (2.8k followers) on Product Hunt. Together, these topics include over 84.7k products, making this a competitive space to launch in.
Who hunted OB-1?
OB-1 was hunted by Tash Ahmed. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how OB-1 stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Tash Ahmed
the auto-fix-until-tests-pass loop is the part I'd want to poke at. tests going green and the code actually being correct aren't the same thing - what stops it from taking the easier path when it's stuck, like weakening an assertion or patching the test itself instead of the real bug?