Problem
When the opencode content filter flags and blocks a response, the user is still billed for the full token generation cost. The user receives nothing — no output, no partial result — but pays as if the response was delivered successfully.
This is a systemic billing issue, not a one-off bug.
Evidence
In my case (documented in #35475), I was charged ~$20 across 3 cache writes where the content filter intervened. The SQLite usage logs confirm tokens were generated and billed, but zero output was delivered to the user.
Expected behavior
If the platform's own content filter blocks a response before delivery:
- The user should not be charged for that generation
- Or the charge should be automatically reversed
- At minimum, there should be a clear refund mechanism for filter-blocked output
Current behavior
- User is charged full price
- Output is blocked
- No automatic refund
- No manual refund process visible to users
- Support issues are closed without human response
Impact
This creates a trust problem. Users cannot confidently use the platform if they risk being charged for output they never receive due to the platform's own moderation system.
Related: #35475, #35643
Problem
When the opencode content filter flags and blocks a response, the user is still billed for the full token generation cost. The user receives nothing — no output, no partial result — but pays as if the response was delivered successfully.
This is a systemic billing issue, not a one-off bug.
Evidence
In my case (documented in #35475), I was charged ~$20 across 3 cache writes where the content filter intervened. The SQLite usage logs confirm tokens were generated and billed, but zero output was delivered to the user.
Expected behavior
If the platform's own content filter blocks a response before delivery:
Current behavior
Impact
This creates a trust problem. Users cannot confidently use the platform if they risk being charged for output they never receive due to the platform's own moderation system.
Related: #35475, #35643