Funny, I solved this problem by having Claude write a pi extension<a href="https://github.com/Pyrolistical/pi-notify" rel="nofollow">https://github.com/Pyrolistical/pi-notifyNow my pi agent setups its own trigger to notify itself when a background process is done
Right! It’s not really rocket science. I’ve been thinking of building a general “wait” command that just blocks until some event occurs. Still more “active” waiting, but as far as I understand the efficiency problem comes from polling.
pyrolistical · · focus · HN ↗
<a href="https://github.com/Pyrolistical/pi-notify" rel="nofollow">https://github.com/Pyrolistical/pi-notify
Now my pi agent setups its own trigger to notify itself when a background process is done
solarkraft · · focus · HN ↗