What they did
The poster, a developer who sits at a PC most of the day, missed a fox taking shoes from outside the door and only saw it later in the recordings. They wanted the camera to come to the screen instead. They wrote the spec and made the design calls, and Claude Code wrote most of the code for FrigatePiP: a small app that listens to Frigate events over WebSocket or MQTT and opens a corner window with that camera's live stream, closing it once motion stops. It ships as a Windows tray app and for Linux desktops, framebuffers and terminals, with filters by camera, object, zone and confidence. The poster reviewed the code and approved each pull request, and tested it against their own cameras.
How it went
The app works and the poster runs it daily. They say it idles at 5 to 10 MB of RAM on Windows with near zero CPU, decodes H.264 and H.265 in hardware and falls back to MJPEG or snapshots. It made Frigate's Third Party Extensions list. A commenter running it on a Raspberry Pi 4 next to a Home Assistant dashboard said it was a big improvement on their previous setup. The framebuffer mode had not been tried on a real Pi before release.
Worth knowing
The Windows installer is unsigned, so SmartScreen warns on install. With the Home Assistant Frigate add-on, port 5000 is off by default and must be enabled, or use 8971 with a viewer user. It needs Frigate for detections, so a Reolink NVR alone will not work.