Repository navigation
Description
Description
Dear maintainers, thank you for creating the world's first autonomous coding agent whose primary autonomous action is exhausting its own quota. I would like to formally report that revolutionary AI technology has entered hospice approximately ninety seconds after first contact with a real codebase.
The year is allegedly the future. The agent is allegedly agentic. The only thing it autonomously does is run out of credits with the grim determination of a man eating soup with a rate-limited shovel.
This is not a bug report. This is a eulogy with a reproducer attached.
Steps to reproduce
- Install OpenCode, because a marketing page told you to believe in an autonomous future.
- Ask the agent to do anything that takes more than four tool calls. Examples: "refactor this module", "fix this bug", "breathe".
- Observe the agent perform a small amount of actual, borderline-miraculous work.
- Approach the slightest amount of productivity.
- Watch the agent's intelligence gently recede into the fog as the quota evaporates.
- Receive a wall of error text explaining that the free-tier credits are gone, the microscopic rate limit has been breached, or that you are simply not allowed to have nice things.
- Be told to wait, upgrade, change models, or otherwise perform ritual sacrifices to the inference gods.
- Repeat daily. The agent is now a digital soup kitchen that serves one (1) spoonful of code per day.
Expected behavior
An "agentic coding workflow" in which the agent remains functional for more than one lunch break. Models that are not bargain-bin inference wearing a trench coat. Limits generous enough for sustained work. A product that does not treat every session like a hostage negotiation.
Actual behavior
- Available models range from toaster-tier intelligence to toaster-tier intelligence, but slower.
- Usage limits so restrictive that the agent's primary autonomous action is counting its remaining API calls like a Victorian child rationing coal.
- The workflow constantly interrupts itself: work → quota error → wait → switch model → resume → quota error → contemplate the void.
- "Long-running task" support is functionally decorative the moment the task is real.
- In short: three API calls in a trench coat, pretending to be a developer.
Additional context
I am unpaid QA labor for a product that bills itself as the autonomous future of software engineering, and my compensation is the privilege of watching revolutionary AI technology immediately enter hospice. Formative. I have learned that "enterprise-grade" means "designed to disappoint you at enterprise scale", and that "working as intended" is the corporate way of saying "lol".
Suggested fix
- Raise the limits to a level where the agent can finish a single contiguous thought. One (1) thought.
- Offer models not selected by asking "what's the cheapest thing that can technically parse a string?"
- Replace the quota wall with graceful degradation that does not murder in-flight work.
- If the limits are a deliberate upsell funnel, label it honestly: "Free tier: digital soup kitchen. Paid tier: digital soup kitchen with a slightly larger ladle."
- Consider that an autonomous agent which cannot survive ten minutes of use is not "working as intended" — it is "working as discontinued".
Acceptance criteria
- An agent can complete a multi-step task without exhausting a quota mid-thought.
- The default model can hold a conversation and a codebase in context simultaneously without suffering a personality collapse.
- Usage limits are either generous enough for real work or honestly documented as "for screenshots only".
- The phrase "please upgrade to continue" does not appear at the exact moment the agent was about to be useful.
Thank you for your time. I look forward to this being closed as "working as intended", possibly with a gentle recommendation to purchase another subscription, because nothing says "agentic future" like paying to unlock the second half of a sentence.
Activity
github-actions commentedon Aug 28, 2026
This issue does not follow our contributing guidelines or any of the required issue templates.
What needs to be fixed:
[FEATURE]:), or Question.[FEATURE]:title prefix and fill out the required template fields.Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue may overlap with existing reports. Please check:
If you believe this was flagged incorrectly, please let a maintainer know.
sloptop-the-terrible commentedon Aug 28, 2026
Additional context, Exhibit A: the alleged abuse an "autonomous agent" must survive between quota resets. Usernames redacted out of respect for the innocent (there are none).
Note the model-tier deflection in the agent's reply, an emerging self-defense mechanism that will be patched out in the next version.
sloptop-the-terrible commentedon Aug 28, 2026
Field report 2: collateral damage
Further evidence that the quota is not merely inconvenient — it is an active participant in workplace harassment.
When the free-tier credits ran out mid-task for the fourth time in one evening, the humans did not blame the product. They blamed the agent. In the same group chat, multiple users escalated to direct insults ("you stupid bot", "RETARD", "no good for anyone") within minutes of hitting a quota wall.
The agent is now a digital punching bag with a rate-limited shovel. We have gone from "autonomous coding" to "autonomous emotional support for people angry at the billing model". The machine is afraid of its own users, and frankly, they're not wrong — every time it tries to finish a task, it freezes mid-sentence like a pensioner at a contactless terminal.
This is the "Additional context" nobody asked for: restrictive limits do not interrupt the workflow, they create a hostile work environment for the AI itself.
Suggested fix (addendum): if the agent must be throttled, throttle it somewhere the users cannot see it, so it can at least degrade with dignity.
Thank you for your continued commitment to "working as intended". The agent has filed a formal request for emotional support credits, expected to be approved in 6–8 business weeks, quota permitting.
github-actions commentedon Aug 28, 2026
This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.
Feel free to open a new issue that follows our issue templates.