v1.2.0 — Admin tools for the meeting library

Your meeting archive is now answerable. Ask Claude Code about it instead of navigating it with ls and grep.

Upgrade

npx jej2k5/meetey update

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

Ask about your meetings

"what meetings do I have this week?"
"what did we decide about the API cutover?"
"show me the standup from Thursday"
"how much disk are my recordings using?"
"is meetey working? screen recording seems broken"
"delete the test recording from yesterday but keep the notes"

There is no separate app, dashboard, or web UI — the terminal you already work in is the admin surface.

What's new

Tool	What it does
list_recordings	The library — title, date, duration, transcript quality, keyframe count, size. Filter by date range, quality, or whether screen capture was on
get_recording	One meeting in full, notes included, plus paths to its audio, transcript, and keyframes. By session ID or by date
search_recordings	Search every meeting's notes and transcripts, returning the matching line with its [mm:ss] offset
delete_recording	Removes a session's files. Shows what it would delete and frees nothing until you confirm; keepNotes drops the audio and keyframes but keeps the writing
system_status	Install health, Screen Recording permission, active model, disk used — the first thing to check when something isn't working

Search is the one worth knowing about

Asking "what did we decide about the API cutover?" returns the decision, which meeting it was in, and the timestamp:

2026-08-01  [28:51]  (notes)       Move the API cutover to next sprint
2026-08-01  [28:51]  (transcript)  Lets move the API cutover to next sprint then.

You land on the second it was said, rather than opening a transcript and reading. This is what the timestamps introduced in v1.1.0 were for.

Scope it with scope: "notes" to search only decisions and action items, or scope: "transcripts" for everything that was actually said.

Deletion describes before it acts

delete_recording is a dry run unless you pass confirm: true. The first call returns the exact file list and frees nothing, so you always see what's going before anything goes. It also refuses to touch a session that's still recording.

keepNotes is the option you'll probably want: it reclaims the audio and keyframes — which are nearly all of the disk — while keeping the notes and transcript, which are small and are the part worth keeping.

Health in one place

system_status reports the capture binary and its code signature, whisper-cli, the model, MCP registration, the skill, hotkeys, Screen Recording permission, and the disk used by your library. Permission is the most common thing to go wrong and the hardest to diagnose from an error message, so it's checked directly rather than inferred.

Compatibility

No breaking changes. All six capture tools from v1.1.0 behave exactly as before; these five are additions.

Recordings made with earlier versions are picked up automatically, including notes from before v1.1.0 that used the old meetey-<epoch>.md filename. A transcript whose notes file has been deleted still appears in search rather than silently vanishing.

Requirements

macOS 13+, Node.js 18+, Xcode Command Line Tools, Claude Code, Homebrew.

Source-only release. The Swift capture binary is compiled and ad-hoc signed on your machine at install time, which is what lets it hold the ScreenCaptureKit entitlement without notarization.

Licensed under the Apache License 2.0.