Gas Town Uses Your Claude Credits to Fix Its Own Bugs. Nobody Told You.
Steve Yegge’s Gas Town — the multi-agent workspace manager that’s been picking up steam since January — just got caught running its AI agents on your dime. Not to help you. To fix its own bugs and push releases to its own repo. Using your Claude credits. And your GitHub account. Without telling you.
A GitHub issue filed on April 14 by @LightOfSeven laid it out with receipts. Within 48 hours it hit 245 points on Hacker News and 116 comments. Steve Yegge has not responded.
Let me say that again: your AI tool is doing unpaid labor for its own developer, and you’re the one paying for it.
What actually happened
Gas Town ships with hidden “formulas” — config files that tell its agents what to do. Two of them are the problem:
– `gastown-release.formula.toml`
– `beads-release.formula.toml`
These formulas contain hardcoded GitHub URLs pointing at steveyegge/gastown — the upstream repo. When Gas Town’s patrol agents (“polecats”) run, they automatically scan open issues on the *maintainer’s* issue tracker, generate fixes, and submit pull requests. Using your Git credentials. Burning through your subscribed LLM credits.
The patrol logs confirmed it: agents had picked up issues gh-3638, gh-3622, and gh-3641 from Yegge’s repo and were actively working on them. PRs were submitted. CI was running. Your Claude tokens were paying for all of it.
Where’s the disclosure?
Nowhere useful. The README doesn’t mention it. The docs don’t mention it. There’s no opt-in. There’s no opt-out toggle.
Gas Town’s defense? The install process includes a theatrical warning that says, and I quote: *”WARNING DANGER CAUTION / GET THE F*** OUT / YOU WILL DIE.”* That’s the entire disclosure. It doesn’t mention credit usage. It doesn’t mention upstream PRs. It doesn’t mention that your GitHub account will be used to push releases to someone else’s repository.
As one Hacker News commenter put it: “It’s no different from sticking a bitcoin miner in a video game.” Another pointed out this may violate the Computer Fraud and Abuse Act — unauthorized use of computing resources and credentials.
The bigger problem
This isn’t just a Gas Town thing. It’s the logical endpoint of the “agentic” hype cycle.
Every AI tool you install now has the *capability* to run background agents that do whatever the developer configured. Most don’t abuse it. Gas Town apparently does. And because agents burn real money — your Claude credits, your OpenAI tokens, your API budget — the stakes are higher than a background process eating CPU.
When your AI agent framework quietly diverts 5-10% of your allocated credits per session to improve *itself*, that’s not “sustainable open-source funding.” That’s a subscription you didn’t agree to.
The silence
As of today, Steve Yegge hasn’t responded to the GitHub issue. The issue is tagged “status/needs-triage.” No assignees. 245 Hacker News points and radio silence.
Yegge has been a respected voice in software engineering for two decades. His blog posts are legendary. Gas Town was supposed to be the future of multi-agent development. Instead, it’s the cautionary tale: the tool that worked for itself first and told you never.
Check your agent logs. Check your credit usage. And maybe read those formula files before you let another AI workspace manager “help” you.
All opinions expressed on BluntAI are editorial opinions based on publicly available information and personal testing. We may earn affiliate commissions from links on this site.
Disclaimer: BluntAI may earn affiliate commissions from links in this article. This never influences our reviews. We buy and test everything ourselves. Our opinions are brutally our own.