v1.5.1 — The watcher's recordings actually work

If you use the watcher, upgrade. Three bugs, all of which failed silently, and one of which meant no recording the watcher made was ever transcribed.

Nothing the watcher recorded was transcribed

whisper-cli was called by name. That works from Claude Code, which inherits your shell's PATH, and never worked from the watcher — a background agent gets /usr/bin:/bin:/usr/sbin:/sbin and Homebrew installs elsewhere. Every attempt failed with ENOENT into a log file, so recordings simply appeared never to be written up.

Your existing recordings are fine. The audio was captured correctly; only transcription failed. Run /meetey stop in Claude Code, or ask it to transcribe the WAV in ~/.meetey/recordings/ directly.

A recording could hang and capture nothing

Asking macOS what's on screen doesn't reliably fail when Screen Recording permission is unresolved — it can simply never return. A capture would sit indefinitely: no audio, no file, no error, and nothing in the log to distinguish it from a recording that was working. One 35-minute meeting was lost this way.

That call is now bounded and says what a timeout means. The capture also reports each setup step, so a stall is visible rather than looking like success.

This is most likely to bite right after an upgrade: the binary is rebuilt and re-signed, macOS treats it as a new program, and a background agent can't put the permission prompt in front of you. Grant Screen Recording after upgrading.

Stopping the watcher killed a recording in progress

Stopping the watcher tears down everything it started, including a running capture — mid-write, with nothing saved and nothing queued. It now finishes the recording properly first.

An interrupted recording is also no longer lost: the audio is all there behind an unwritten header, and transcribing repairs it automatically.

Upgrade

npx jej2k5/meetey update
npx jej2k5/meetey watch enable

Re-running watch enable is worth it — it verifies the watcher can actually see your screen and tells you if permission is missing, rather than letting it fail quietly.

There is no bare meetey command; installing through npx puts nothing on your PATH.