Skip to content

Bug: Content filter blocks output but user is still billed for full generation cost #35643

Description

@arshbuttar426-hue

Description

When the opencode content filter flags and blocks a response, the user is still billed for the full token generation cost. The user receives zero output but pays as if the response was delivered.

This is a billing system bug — the charge should not be applied (or should be reversed) when the platform's own guardrail prevents delivery.

This is related to but distinct from my incident in #35475. That issue documents a specific false-positive charge. This issue identifies the systemic bug that allows the charge to happen in the first place.

OpenCode version

Latest (authed via GitHub CLI, using opencode CLI)

Steps to reproduce

  1. Generate a response that triggers the content filter (false positive)
  2. The output is fully blocked — user sees nothing
  3. Check usage logs — tokens are billed as if the response was delivered
  4. User is charged for output they never received

Plugins

None

Operating System

macOS (Apple Silicon)

Terminal

iTerm2

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions