Verified purchaser
AMAZING founder who really wants this to work
Updated my original review to 5 tacos after outstanding support from the founder and a fix that’s working well in my testing so far.
***
I started using Headroom with Claude Code in VS Code and the terminal for smaller coding projects, and my first impressions were very positive: the token savings were real—and substantial. The quality of the code didn’t seem to suffer either, so I was almost ready to leave a 5-taco review.
Then I ran into errors and timeouts in specific situations, mostly on larger projects involving lots of MCP calls and connected apps. I got frustrated enough to leave a negative review here on AppSumo, to which Garm, the founder, responded almost immediately.
After I sent him details of the technical issues, he took them seriously and promised to investigate. By the next morning — just 10 hours (!!!) after I’d posted my initial review — I had an email from him saying he’d pinpointed the bug and shipped a fix.
I started testing the fix today, and so far, so good! :) It’s still early, but I’m very encouraged — and I’ll continue to report any other issues I come across.
What really stood out was how Garm handled the situation. He was helpful, respectful, and quick to act. He took a frustrating customer experience and turned it into a reason for me to feel more confident about the product and trust the person behind it.
So, between the substantial token savings I’ve seen and the founder’s responsiveness when something went wrong, I’m excited about Headroom’s future. They’ve definitely won me over as a customer and fan!
Garm_Headroom
Oct 8, 2026Hi Vikingfinity!
Thanks for sharing this experience, this definitely shouldn't be happening!
We use Headroom on large projects ourselves every day, with long sessions, many skills and several MCP servers, so project size alone shouldn't cause this.
Most likely, something specific in your setup is going wrong that we need to fix.
To figure out what, could you share the following with us via email on [email protected] ?
- The output of this command in a terminal, from the machine you experienced this on:
grep -h -B3 -A3 -E " 502|timed out|Request failed" ~/.headroom/logs/proxy-*.log | tail -150
- Which MCP servers were connected in that session, especially the one you used for image generation
- Roughly when the 502s started (date / time)
That should be enough to figure it out.
Garm