[BUG] Spontaneous "Request interrupted by user" triggered by Linux kernel 6.17.0-19-generic

Resolved 💬 3 comments Opened Mar 18, 2026 by c20h30o2 Closed Mar 22, 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 spontaneously shows "[Request interrupted by user]" without any user action (no Ctrl+C, no Escape pressed). Once triggered, subsequent commands in the same session
are also immediately interrupted, making the session unusable. The only workaround is to /exit and start a new session, but the issue recurs.

Root cause identified: the issue is caused by Linux kernel 6.17.0-19-generic. Downgrading to kernel 6.17.0-14-generic completely resolves the problem. Extensive tool-call stress
testing on 6.17.0-14 shows zero interruptions.

What Should Happen?

Claude Code should not be interrupted unless the user explicitly presses Escape or Ctrl+C.

Error Messages/Logs

Steps to Reproduce

  1. Boot Linux with kernel 6.17.0-19-generic (Ubuntu 24.04)
  2. Run claude in terminal
  3. Use Claude Code normally, especially triggering tool calls (Bash, Read, Grep, etc.)
  4. After a few tool calls (often when tools return large output), the session spontaneously shows "[Request interrupted by user]"
  5. All subsequent commands in the same session are also interrupted

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.78

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

  • Tested with both Node 18.19.1 and Node 22.22.1 — issue persists on both
  • Tested inside and outside tmux — issue persists in both
  • Tested with single and multiple Claude instances — issue persists
  • Downgrading to kernel 6.17.0-14-generic completely resolves the issue
  • The interruption appears more likely when tool calls return large output
  • Related issues: #21477, #23350

View original on GitHub ↗

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