You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
[0.0.7] - 2026-11-20
Added
List snapshotwisprflow.meetings.list (output: "list"). An app can bind it and render meetings without
knowing Wispr Flow. It is the tools RPC method events_list with { "source": "wisprflow", "list": "meetings" }:
the model tool's schema has no list, so an agent sees no list. It calls the existing search_meetings read, not a
second client, over the last 29 days and returns at most 50 meetings, newest first, each an id and a title; a title is
screened whole and then cut to 200 characters, control characters are stripped, an id appears once, and the answer
stops short of 64 KiB. It has no cursor. wisprflow.meetings stays the events
source and is not renamed, and no write is declared.
Changed
Source contract @we-the-rebel-alliance/source-contract v0.3.0 (was v0.2.0), a devDependency bundled into dist/
(no runtime dependency). The declaration and the probe answer are unchanged: the plugin sends none of v0.3.0's new
keys (facts, hints, routines, an actor's kind, sections or parts), which a consumer still on v0.2.0
refuses. The conformance test names the seven v0.3 checks the source carries nothing for, each with its reason.
A listing still reads every sign-in as the free plan, because no Wispr Flow tool names the plan: a read that starts
more than 29 days ago answers gap: { reason: "expired" } once and lists from 29 days ago, so a meeting the plan has
locked is never skipped silently.
Known limits
Meetings need Cloud Sync. A meeting recorded while Dictation cloud storage is off never appears, even after you turn it on.
Some Wispr Flow data is out of reach. No tool reads dictation history, the dictionary, snippets, styles, usage stats or Notetaker chat, and no tool takes audio.
The tool list depends on the account. An active HIPAA agreement or an organisation policy can turn Wispr Flow's MCP off, and a tool the plugin has not classified runs at the access value you set.
The meetings source sees what Wispr Flow's MCP sees. Wispr Flow's MCP needs Notetaker and MCP access, Cloud Sync, no active HIPAA agreement and no organisation policy that turns MCP off; it answers "Too many requests" when queries come too fast, publishes no number for that limit, and asks you to wait about a minute (Wispr Flow). A listing reads search_meetings once per page of 200 meetings of each week, from up to a week behind its cursor, to find a meeting that reached Wispr Flow late. Wispr Flow names no account, so the source's owner is unverified (OpenCode's sign-in, not a Wispr Flow identity): its id is the sign-in's credential id and its label is for display only, so after any new sign-in an old cursor is refused with ACCOUNT_MISMATCH, and a consumer starts again. On Wispr Flow's free plan, meetings older than 30 days are locked, and Wispr Flow names no plan, so a listing reaches back at most 29 days on every plan, a day inside the lock: one that starts earlier answers a gap (expired) once and lists from 29 days ago. A minute Wispr Flow caps (more than 1000 meetings) answers a gap (window-truncated) and the listing moves past it. A meeting that reaches Wispr Flow after the cursor passed its start (processed late, uploaded from a Mac that was offline, or shared later) is listed on a later read, once, while it started at most a week, or 48 meetings (more when they share a start), behind the cursor. A meeting you delete before it is listed is never listed, and one already listed is not withdrawn.
The meetings source's test data is invented. The conformance kit runs on a synthetic Wispr Flow whose answers follow the JSON shape Wispr Flow's live search_meetings returned when last checked; their content is made up, not live-verified. Its report is complete: the expired-cursor and gap checks run on a cursor older than the 30-day window, and only the check on failed[] is not applicable, with its reason in the report: every meeting comes whole from a search_meetings listing and a failed call fails the whole read, so no single meeting fails on its own.
Attendee contacts are readable at every access value.get_participant_contacts is a read, so it is allowed unless you add a rule for it.
Tested on OpenCode 2.2.3, 2.2.4, 2.2.5, 2.2.6, 2.2.7, 2.3.0, 2.3.1 and 2.3.2. Other releases inside >=2.2.3 <2.4.0 start, and status reports them as untested.
Jelly. The access setting declares its choices, which a Jelly needs app#1301 to read; an older Jelly turns the declaration down.
Updates are not automatic for a Git install, and opencode plugin update and opencode plugin check do not work on one: to move to a newer release, remove the old entry and add the new tag.