Send the frame, not the keys

A client asks what the dashboard looks like right now. The old workflow: screenshot, crop, save, open the chat app, drag, wait. The new one is two curls: the display's screenshot endpoint piped straight through with a filename:

curl .../api/v1/display/screenshot | curl -T - .../api/v1/pipe/friday?filename=dashboard.png

They open the pipe URL. The browser downloads dashboard.png: the exact pixels on your container's screen at that second, streamed through, stored nowhere in between.

You could send the display URL instead, but a URL to a live session is a key, and it keeps working after the question is answered. Some moments call for a photograph, not a visit.