Skip to content

v2.0.0 — Recording you can rely on

Latest

Choose a tag to compare

@jej2k5 jej2k5 released this 06 Aug 21:11

The first version I'd trust with a meeting that matters.

1.4 and 1.5 lost recordings — repeatedly, in ways that were hard to see. This release fixes the cause and removes the conditions that let it hide.

What was wrong

The meeting watcher checked for windows every ten seconds, including while a recording was running. macOS treats a second look at the screen as a competing capture and terminates the live one, so recordings died a few seconds after starting.

It arrived as an improvement: keep reporting whether the watcher can see your screen, even mid-recording. It destroyed the thing it was reporting on.

The timeline was plain in the logs — a recording made before that check was introduced ran 34 minutes; every recording after it died in seconds.

Why it survived being fixed

Two reasons, both fixed here:

  • Updating didn't restart the watcher. macOS keeps running whatever it loaded at login, so the old code kept running and kept killing recordings while the update appeared to have worked.
  • The self-check passed while the bug happened in front of it. It reported "0.3 seconds written" of a six-second test as a tick, because it only asked whether any audio arrived. A capture that stops early is exactly the fault it exists to catch.

Nothing is lost any more

The audio file is valid at every moment while it's being written, not only once it finishes cleanly. Lose power, kill the process, close the laptop — whatever is on disk plays and transcribes up to that second.

Earlier versions wrote the file's header only at the end, so any interruption in an hour-long meeting destroyed all of it.

Transcripts arrive on their own

Within about a minute of a meeting ending, a readable timestamped transcript appears in ~/.meetey/recordings/. No Claude Code, no sign-in, nothing to remember — transcription runs locally.

Notes still need Claude, so they wait for you. /meetey writeup writes them for everything that piled up while you were away.

Also

  • Screen capture covers the whole app. Narrowing it to a single window cost four recordings — Google Meet replaces its window when you join a call, and a capture aimed at the old one dies, taking the audio with it. Close or mute anything sensitive before opting in.
  • A second meeting in the same window gets offered. Previously an instant Meet started after an earlier call was silently never suggested.
  • npx jej2k5/meetey verify proves the machine can record and transcribe, by doing both. Install and update run it and decline to claim success when it fails.

Upgrade

npx jej2k5/meetey update

Then restart Claude Code. Grant Screen Recording permission if macOS asks — the binary is re-signed on every update, so it's treated as new.

If you had recordings that never produced notes, they're still there: /meetey writeup.