Who is meant to pay for bugs?

### What happened?

Gemini CLI burns 6 million input tokens in about 1h because it can't edit files.

### What did you expect to happen?

Ideally the `replace` tool would be used correctly by Gemini CLI (this is a known bug) but the higher-level fix would be to account for API usage caused by the tool's own bugs differently than normal API usage.

Specifically, when Gemini CLI falls back to an approach that uses a lot of input tokens — in this case, reading and rewriting entire files instead of doing a simple replace — the resulting input tokens should not be deducted from the user's rate limit. Probably that's next to impossible to implement, but an alternative would be to automatically credit the user with a temporary rate limit increase for each instance of the bug to cover its cost.

### Client information

```console
About Gemini CLI │
│ │
│ CLI Version 0.1.18 │
│ Git Commit cd7e60e0 │
│ Model gemini-2.5-pro │
│ Sandbox no sandbox │
│ OS darwin │
│ Auth Method gemini-api-key
```

### Login information

Auth Method gemini-api-key

### Anything else we need to know?

I was also confused into buying Pro for the web interface which is of no interest to me. I will need to cancel that, since it has no effect on rate limits in the Cloud product. The naming is very confusing.