v1.4.2 — The watcher can tell you it's working

If you use the watcher, upgrade. It could previously run without seeing anything, and say nothing about it.

The watcher could be on and blind

macOS grants Screen Recording permission per process, so the watcher needs its own — separately from the one meetey-capture already has. Nothing asked for it, so most people wouldn't have granted it.

Turning the watcher on reported success regardless. It would then look for meetings, see nothing, write one line to a log nobody was pointed at, and repeat every ten seconds. No error, no prompt — just a watcher that never noticed a meeting, with no way to tell whether it was broken or you simply hadn't had one.

Enabling now checks before it congratulates itself, and if it can't see your windows it says so and names exactly what to switch on. Nothing is left installed that looks on but isn't.

The check runs from the agent itself rather than the installer, because permission is attributed to whichever process asks — a check run from the terminal would pass while the thing it just installed stayed blind.

Back-to-back meetings were missed

When a recording ended, the watcher transcribed it — and froze completely while doing so. On an hour of audio that's several minutes of being switched off, so a meeting starting right after one ended was missed entirely. Transcription now runs alongside the watcher rather than in front of it.

Status commands were quietly wrong

• /meetey status said nothing was happening while a finished recording sat waiting to be written up — right after a notification told you to go collect it.
• /meetey doctor, whose whole job is answering "is meetey working?", couldn't see the watcher at all. Now it reports whether the watcher is on and whether it can actually see anything.

Update checking

npx jej2k5/meetey status

now reports whether a newer version has been released.

This is the only part of Meetey that contacts a server. It's an anonymous request for the repository's latest release tag — nothing about you or your machine is sent. Cached for a day, two second timeout, skipped silently when offline. MEETEY_NO_UPDATE_CHECK=1 turns it off. /meetey doctor reports the same figure but never makes the request itself; it reads what the CLI last found.

Also

• Enabling stopped claiming "audio only", which stopped being true when the prompt gained an audio + screen option.
• A meeting you skipped stays skipped across a restart.
• npx jej2k5/meetey watch log and ... watch logs both work.

Upgrade

npx jej2k5/meetey update

Then restart Claude Code. If you had the watcher enabled, run npx jej2k5/meetey watch enable again — it will now tell you whether it can actually see your screen.

(There is no bare meetey command: installing through npx runs the package from its cache and puts nothing on your PATH. Earlier notes said otherwise — that was wrong.)