[BUG] Non-stop polling with 100 millisecond timeout

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 process calls epoll_pwait2 with 100 millisecond timeout non-stop. See the attached strace.claude.log.zip.

That burns CPU cycles and prevents the CPU from entering low-power states, wasting electrons for nothing.

Polling is a programming anti-pattern that shouldn't pass through a code review.

Can you guys fix this programming blunder in the claude code executable by removing any and all polling, so that claude process doesn't burn any CPU cycles for doing nothing, please?

What Should Happen?

claude process doesn't use any CPU when unused.

Error Messages/Logs

strace.claude.log.zip

Steps to Reproduce

1. Minimize the terminal window running claude process.
2. Open htop with update interval of 2 seconds, and observe claude process 0.5-1.5% CPU usage non-stop.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.0.75

Platform

Other

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

System details:

claude --version: 2.0.75 (Claude Code)
terminal: konsole 25.12.0

Operating System: KDE neon User Edition
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1
Kernel Version: 6.8.0-90-generic (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5825U with Radeon Graphics
Memory: 64 GiB of RAM (62.2 GiB usable)
Graphics Processor: AMD Radeon Graphics
Manufacturer: Dell Inc.
Product Name: Inspiron 14 7425 2-in-1
System Version: 1.23.0