Goose stops responding without any error message once conversation hits context limit on openrouter.

[myevolve]

Describe the bug
Goose will eventually just stop responding and not display the error message from the llm, in this case, openrouter using anthropic/claud-3.5-sonnet

To Reproduce
Steps to reproduce the behavior:

1. Build for long enough to exceed 200K context.

Expected behavior
Expected behavior is that Goose would use the middle out transform and compress prompt to context limit or just below it so it doesn't fail.

Screenshots
Trace from langfuse:
This endpoint's maximum context length is 200000 tokens. However, you requested about 201326 tokens (197771 of text input, 3555 of tool input). Please reduce the length of either one, or use the "middle-out" transform to compress your prompt automatically.

Please provide following information:

• OS & Arch: [Ubuntu 24.04 x86]
• Interface: [CLI]
• Version: [v1.0.7]
• Extensions enabled: [Developer,Computer Controller, Memory,Fetch,Git,Github]
• Provider & Model: [openrouter:anthropic/claude-3.5-sonnet]

Additional context
Add any other context about the problem here.

[yingjiehe-xyz]

@myevolve thanks for reporting it, previously we have some discussion about the truncate on goose for all providers, will update here later

[CyphrRiot]

This has been ongoing and since 1.0.1 at least. I've reported it many times. Be nice to fix this once and for all, because the console (CLI and GUI) failure is not at all descriptive of the issue.

[salman1993]

@HunterR0se I believe this specific error is coming from OpenRouter - https://openrouter.ai/docs/features/message-transforms

However, in the case that OpenRouter doesn't handle context length errors, Goose should try to do a better job at truncating.

[pfergi42]

Bump. This is the biggest issue I'm having recently. It requires restarting a new goose session, and then having to get goose up to speed all over again.

[CyphrRiot]

Bump. This is the biggest issue I'm having recently. It requires restarting a new goose session, and then having to get goose up to speed all over again.

Exactly! And the amount of tokens and API calls to do this is both mentally (and financially) burdensome at the least and infuriating at most.

I love goose, but this really is a "show stopper" issue for the project.