Generation terminates on unstable networks instead of retrying/resuming

[Manni1000]

What version of Kimi Code CLI is running?

kimi, version 1.22.0

Which open platform/subscription were you using?

kimi code Allegretto

Which model were you using?

kimi-for-coding

What platform is your computer?

Linux 6.11.11-valve26-1-neptune-611-gb3afa9aa9ae7 x86_64 unknown

What issue are you seeing?

When using kimi-cli /kimi web over an unstable mobile hotspot connection with high latency, network interruptions cause the generation to terminate completely rather than pausing and retrying/resuming once connectivity returns.

• Connection drops immediately on network instability
• Generation stops mid-stream without recovery
• Requires manual restart of the query

What steps can reproduce the bug?

1. Connect via mobile hotspot with high latency or packet loss
2. Start a long generation: kimi "explain quantum computing in detail"
3. Simulate network instability (toggle airplane mode briefly, or move to dead zone)
4. Observe that generation terminates instead of waiting/resuming

What is the expected behavior?

Expected Behavior

The CLI should:

1. Detect connection interruptions
2. Resume streaming from the last successful chunk/position
3. Or at minimum, wait longer before giving up on high-latency connections

Additional information

No response

[mvanhorn]

Submitted a fix in #1544 - httpx.ProtocolError (RemoteProtocolError on mid-stream disconnect) wasn't being mapped to a retryable error type.

[Manni1000]

i also get sometimes this message "Error code: 401 - {'error': {'message': 'The API Key appears to be invalid or may have expired. Please verify your credentials and try again.', 'type': 'invalid_authentication_error'}}"" but its still generating when i try again. what could cause this?