v1.4.0 — Recordings that start on offer and end by themselves

Meetey no longer needs you to think about it during a meeting. It can notice a call starting and ask, it shows what it is capturing while it runs, and it stops on its own when the call ends.

Upgrade

npx jej2k5/meetey update

Then restart Claude Code so the MCP server reconnects. New installs: npx jej2k5/meetey install.

Changed behaviour

Existing recordings work differently after this upgrade, without you asking:

• Recordings end themselves — when the app quits, when the captured window closes, or when the call itself ends. The last of those trims the file back to when the call ended, so the waiting never reaches your transcript.
• A menu bar item appears while recording, showing what is being captured and for how long, with Stop Recording.

Both are on by default. autoStop: false, stopWhenCallEnds: false, and menuBar: false on start_recording turn them off individually.

Far fewer keyframe files

Screen capture used to write a JPEG whenever the picture differed from the last one. In the standard slide-plus-speaker-tile layout the moving tile always qualified, so a one-hour call filled its 200-frame budget in the first few minutes and recorded nothing after.

Two rules replace that:

• A keyframe is written when the screen stops moving, not when it starts, so a slide transition collapses to the one settled frame — which also reads far better than anything caught mid-fade.
• Regions that are always moving stop counting. A speaker tile, a progress bar, a clock.

Revisiting a slide you already showed no longer writes it twice; the manifest records that it came back.

Watch for meetings

npx jej2k5/meetey watch enable

Notices meetings in Chrome, Zoom, and Teams and asks before recording — naming the window, offering audio only or audio + screen. Off until you enable it, and it never starts a recording on its own. Also drivable from /meetey watch inside Claude Code.

Narrow what gets captured

Screen capture can now target a single window rather than everything an app displays, which keeps its other windows and notification banners out of frame. On a multi-monitor setup the display is chosen by where the meeting actually is, rather than whichever display came first.

macOS has no tab-level capture, so a window is as fine as it goes — to isolate one tab, drag it into its own window.

Also

• Transcripts are produced as soon as a watched recording ends, so they are ready before you ask.
• Ctrl+Shift+R / Ctrl+Shift+S are documented as what they are: shortcuts inside Claude Code, not system-wide hotkeys. Stopping from anywhere is what the menu bar is for.
• sceneThreshold is reachable from start_recording; it was previously documented but not wired up.

Requires macOS 13+. After upgrading, macOS may ask for Screen Recording permission again — the capture binary is rebuilt and re-signed. Enabling the watcher asks separately for Node.