I do something very similar. With some hacky string matching you can detect wether a window is available for reception and get past that.

I desire a more robust system which injects the events into the harness directly, but haven't found a way that works across systems.

https://github.com/tcdent/dotfiles/blob/main/bin/agent-messa...

▲

HappySweeney 8 hours ago | parent | next [-]

The hacky string matching is what I started with, but there was always new ghost text. I turned suggested prompts off which helped, but idle hooks plus ensuring the terminal doesn't change over a half second has done the trick so far, and I don't have to keep chasing new ghost text.

▲

andai a day ago | parent | prev [-]

I hooked up Claude Code's "stop" hook to a frog croak, so I know when it's done.

I'm guessing the same hooks could be used to ... Okay I guess there isn't a User Typed But Didn't Send Yet hook... Hmm...

I heard earlier there's a T3 harness which somehow wrangles other harnesses as one big meta harness, but I haven't checked it out yet.

▲

fragmede a day ago | parent [-]

I had my stop hook playing a sound, but I have a couple of them running at the same time so I'd have up figure out which one stopped, so I had Claude change it so the stop hook told me which one stopped.

	▲	andai 18 hours ago \| parent [-]
		With a TTS? Or you mean just using different sounds. Considering both of those options right now. A while back on my phone all the damn notifications sounded the same, so I just made a couple of recordings of myself saying the name of each app and set those as the notifications.