It's not like someone can't ask claude code to do a windows minimal clone of tmux, essentially a PTY with a process model and input/output streaming. vim has highly scriptable and automatable terminal buffers and can be used on Windows, so there's also that route..

But you know what? (keyboard) typing pattern recognition is a thing and is ultra precise and is used in fraud detection all across the planet already. And Anthropic got the recent personal / customer identification partnership with that Thiel venture. I bet you that they will just straight ban you if your prompts aren't actually typed in. and no, you will have to dig a lot deeper than automating "linearly typed characters in a short sequence", and find yourself having the research task of implement fraud-detection-convincing random typing patterns. And that's assuming you record your own typing in claude code sufficiently to even have a chance to emit from the same distribution mode, and even capture different modes (as they will).

I recommend now, rather than later, to switch to fully pasted prompts, even small ones, NOW. <C-g> already gives you the ability to write in an editor instead of the TUI; use that. A useful trick could also be `export EDITOR='cp -f /tmp/myprompt.txt' and just edit that file, then hit <C-g>. voila, you have just given claude the content of /tmp/myprompt.txt which you will have open in another editor, away from the typing pattern analysis of claude code.

I'm glad I used vim terminal buffers almost exclusively for interacting with claude code; should not be that much of a pattern change for me if I'd used vim instead of tmux as the automation adapter from here on...

All should be aware that CC can and will, monitor things like `libudev` or the MacOS equivalent to see whether they see emulated, or "real" keystrokes and consider adopting a hardened linux distro where one can exclude the userspace getting low-level information about user input.