update_meeting refuses to rename Offline Mode meetings, but docs list no such restriction

App version: 1.0.0-rc.31 · macOS: 27.0 (26A428) · MCP client: Claude (claude.ai)

What happens

update_meeting with a title on a meeting recorded in Offline Mode is queued, then fails. get_import_status returns it under recentFailures:

type: meeting_update status: failed reason: "Meeting is in Offline Mode — connected AI tools cannot rename or delete it. Ask the user to do it in the app."

Reproduced on five meetings today and on earlier attempts yesterday, always the same reason. Renaming the same meetings by hand in the app works.

What the docs say

The update_meeting row on mimicscribe.app/docs/integrations reads: "Edit a meeting's library metadata: rename it (title), or delete it (delete: true)." The only stated constraints are one action per call and the warning that deletion is permanent. Nothing about Offline Mode or Local Mode.

The page does document offline restrictions elsewhere — offline meetings are hidden from MCP read tools behind a Settings toggle, correct_meeting refuses them, the webhook never fires for them. update_meeting is not in that list, and the changelog doesn't mention it either.

Why this looks like a bug

correct_meeting refuses offline meetings because applying a correction regenerates the summary through the AI provider, which offline meetings skip. A rename triggers no regeneration — a title is library metadata, not transcript content, and needs no provider. The guard's stated reason doesn't extend to update_meeting.

It also isn't the read-visibility guard: "Allow connected AI tools to read offline meetings" is on here, and search_meetings returns these meetings fine with no hiddenLocalModeCount.

Steps to reproduce

1. Record a meeting with Offline Mode on.
2. Enable Settings > Integrations > "Allow connected AI tools to read offline meetings".
3. From an MCP client: update_meeting(id: , title: "Renamed test").
4. Poll get_import_status → the entry lands in recentFailures.

Expected

Either the rename applies, or the restriction is documented in the update_meeting row and returned as a structured error code (local_mode_meeting / offline_meeting, matching correct_meeting) rather than only as prose in recentFailures.

Impact

I rename generic recordings to their Google Calendar event names weekly so recurring meetings group and search properly. Every offline recording has to be renamed by hand, which is most of them.