Claude Code CLI crashes during context summarization - "Failed to get summary response from streaming"

Resolved 💬 3 comments Opened Jan 9, 2026 by Yanwan93 Closed Feb 23, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Claude Code CLI crashes when automatic context summarization is triggered. The client cannot recover from this error.

What Should Happen?

When context summarization is triggered, the CLI should:

  1. Complete the summarization successfully, OR
  2. If the streaming request fails, the non-streaming fallback should work, OR
  3. If both fail, display a clear error message and allow the user to:
  • Retry the summarization
  • Continue the session without summarization
  • Start a new session without crashing

Currently, the client crashes and becomes unusable. Resuming the session causes the same crash to repeat, making the conversation unrecoverable.

Error Messages/Logs

2025-12-28T22:26:52.150Z [ERROR] Error in non-streaming fallback: Request was aborted.
  2025-12-28T22:26:52.150Z [ERROR] Error: Request was aborted.
      at n4$ (/$bunfs/root/claude:1278:19507)
      at YAB (/$bunfs/root/claude:4548:1430)
  2025-12-28T22:26:52.158Z [ERROR] Error: Failed to get summary response from streaming
      at KQ$ (/$bunfs/root/claude:1703:1226)
      at async BUD (/$bunfs/root/claude:1777:3210)

Steps to Reproduce

  1. Start a long conversation with Claude Code CLI
  2. Continue until context approaches limit (~200k tokens)
  3. Automatic summarization triggers
  4. Client crashes with above error

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.2

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗