WARN goose::providers::openrouter: Failed to get usage data: No usage data in response forces new session.

[myevolve]

Describe the bug
The message "WARN goose::providers::openrouter: Failed to get usage data: No usage data in response" appears and goose stops waiting for input. When this happens, sometimes "try again" or "continue" will work and goose will continue. Most times, a new session is required. And just now, even a new session gives the same error.

To Reproduce
Steps to reproduce the behavior:

1. Start goose and give it a development task
2. The message usually will appear after goose has been running/working for 30-60 min, this includes stops asking for input.
3. When the message appears, sometimes goose will recover and continue.
4. Usually when the message appears, a new session has to be started, resuming session doesn't work.

Expected behavior
The error message doesn't prevent goose from continuing and goose is able to compensate and inform user more details.

Screenshots
If applicable, add screenshots to help explain your problem.

Please provide following information:

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

Additional context
Add any other context about the problem here.

[yingjiehe-xyz]

Hi @myevolve, does it show any error message? Failed to get usage data is a warning, it should not block using goose

[myevolve]

What I mean by blocking goose is that no matter what I type, the same message repeats itself and the only way to get goose working again is to quit and start a new session. There are times it does come back, but I've had to restart the session probably close to equal or more times it came back. The complete message is WARN goose::providers::openrouter: Failed to get usage data: No usage data in response.

[yingjiehe-xyz]

I see, can you add you log here? you can find it under ~/.config/goose/logs/cli/xxx/xxxx.log

[gabcoyne]

The quick fix for this is to open the jsonl file for the session and remove lines where the content array is empty, i.e. [] and change providers. I found that if I change providers without deleting I run into different errors per-provider.

[myevolve]

Thank you @gabcoyne!