Tokens are wrong (dies at 70%) (Anthropic/claude sonnet)

[CyphrRiot]

I am using Anthropic Claude Sonnet 4.

I get this error (crash) when running:

Failed to parse response: Request failed: 
Provider returned error (code: 400) (status 400)
    at crates/goose/src/agents/agent.rs:770

Ran into this error: Request failed: Failed to parse response: 
Request failed: Provider returned error (code: 400) (status 400).

Please retry if you think this is a transient or recoverable error.
Context: ●●●●●●●○○○ 70% (140894/200000 tokens)

As you can see, the context is less than 200,000 tokens (Sonnet 4s token amount), but Goose crashes and runs out of tokens with a terrible error.

[michaelneale]

@CyphrRiot was there more to the error than that? (ie anything else printed out)
were you using the anthropic provider (ie direct to anthropic?) - as we have limited ability to try all the providers so ideally need to know exactly which one (ie not via open router, databricks etc - I use it via databricks so naturally don't see that with the same model, but could be with anthropic provider if it is direct)

[michaelneale]

I am not able to reproduce this, but have no more anthropic credits (if it is direct)

[michaelneale]

I do occasionally see:

Ran into this error: Request failed: Request failed with status: 400 Bad Request. Message: messages.45: `tool_use` ids were found without `tool_result` blocks immediately after: toolu_01Sf6TDaMKK1y49vjqzAziPa. Each `tool_use` block must have a corresponding `tool_result` block in the next message..

[michaelneale]

yeah sorry @CyphrRiot I am at a loss - there seems to be something there (the 70% is interesting, the 0.7 ratio) but I can't make it happen at my end. Are you able to try again with newest release? (and also share your config, and how you reproduce it if you can). I have asked anthropic bout that other error with tool results as it may be related and being hidden.

[michaelneale]

A possible fix: #3311 - but not 100% sure (as can't reliably reproduce anything).

there is also #3194 which may help - @CyphrRiot if you can repro, could provide you with some ad-hoc builds if you wanted to try either to see if it makes it go away.

[michaelneale]

this should be resolved now