8M token in 8 minutes

Before submitting your bug report

• I've tried finding an answer on the Continue docs site
• I'm not able to find an open issue that reports the same bug
• I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS: macOS
- Continue version: v2.0.0-vscode
- IDE version: Version: 1.121.03429
- Model: DeepSeek coder

Description

I'm glad I didn't use Opus. I have a midsize project, just asked to refactor what would take me.. perhaps the whole day but I would have commited the changes.

Churn, after churn, the project eventually passed the build. but the changes were far from satisfactory. I decided to check token usage, and to my surppised it was over 8 millions tokens.

Is this tool valid for anyone, or is it about paying continuously for tokens?

To reproduce

• Checkout an open source project (e.g this one).
• Pick top affordable Frontier model on OpenRouter.
• Sandbox environment
• Ask to refactor or add a feature.
• Go for coffee, be check to confirm and approve even though you said always approve.

Log output

building fails.
building fails.
building fails.
building fails.
building fails.
building fails.
building fails.
....

build passes

The report names no source file, test, or entry point. Reproduce on macOS with Continue v2.0.0 in VS Code, DeepSeek Coder, an OpenRouter model, and a sandboxed project; inspect the logs around the repeated build failures and token usage. Done means the runaway churn and repeated failed-build cycle are understood and covered by a reliable regression check.