[Bug] claude -r freezes keyboard input twice on WSL2: FleetView and session attach require Ctrl-Z recovery

Bug Description
---
Title: claude -r freezes keyboard input twice, every single time — requires Ctrl-Z + fg at launch AND again after selecting a session

Environment:

• Claude Code v2.1.204 (confirmed up to date)
• WSL2, distro Kali Linux, kernel 6.18.33.2-microsoft-standard-WSL2, WSL 2.7.10.0
• Terminal: Windows Terminal
• Shell: zsh + oh-my-zsh + powerlevel10k (instant prompt: verbose)

Symptom (100% reproducible, not intermittent):
Every time claude -r is run:

1. It launches into FleetView (session picker) but keyboard input is completely unresponsive from the start. Recovery: Ctrl-Z (shell shows [1]+ suspended claude -r, prompt segment reports signal TSTP), then fg — FleetView becomes usable.
2. After selecting a conversation to resume, the session freezes again the same way as soon as you try to type/interact in it. Recovery: Ctrl-Z + fg a second time — only then does the conversation actually respond to input.

This two-stage freeze happens on every single invocation of claude -r, with no exceptions observed so far.

Process tree observation (non-frozen snapshot):
Session runs via claude daemon run --origin transient spawning multiple claude bg-pty-host --bg-pty-host <socket> <rows> <cols> -- ... --bg-spare <socket> and claude bg-spare children (background session pool/multiplexing architecture). Suspect the freeze relates to how a bg-pty-host regains/loses the terminal's foreground process group (TPGID) relative to the real pty — possibly an unintended SIGTSTP delivered at both (a) FleetView startup and (b) session-attach handoff.

Ask: Is this a known issue with the bg-pty-host/daemon multiplexing or the -r resume flow specifically on WSL2/Linux terminals? Any debug flag to capture more detail?

Environment Info

• Platform: linux
• Terminal: wsl-kali-linux
• Version: 2.1.204
• Feedback ID: a3b01dee-97c8-4c6a-9096-e6a53b943b60

Errors

[]