What terminal / agentic workflows spawn the demonstrated dialogue boxes that require the User to click/reject the action? Aren't most such flows actually inline UIs? And finally, if the core issue is that these confirmation boxes are tied to the terminal that triggered them, which does not autofocus, what's the point of said "big arrow" that is also lurking behind without focus?
If the said "big arrow" automatically gains focus, isn't the real fix here to just make the dialogue boxes themselves gain focus automatically? Both are similarly disruptive anyway.
"Teach me to use this app myself" kinda stuff. Guiding agent rather than doing agent.
~guywithnopowertodisallowit
Does one need 4 programming languages to draw something on a mac?
- rainbow dripping arrows
- angrily pointing arrows
- flame-surrounded text boxes with particle effects
- the ability for the agent to play airhorn.wav at max volume, overriding existing volume or mute settings
https://donhopkins.com/home/archive/psiber/cyber/pointer.ps
https://youtu.be/_fqCeuue5Ac?t=213
https://medium.com/@donhopkins/the-shape-of-psiber-space-oct...
ForHackernews•43m ago
Grim. If you're just there to click sudo buttons for the bot, you might as well give it root access and be done.
franze•35m ago
gwerbin•32m ago