Repository navigation
Releases
v0.0.7
[0.0.7] - 2026-11-20
Added
- List snapshot
wisprflow.meetings.list(output: "list"). An app can bind it and render meetings without
knowing Wispr Flow. It is the tools RPC methodevents_listwith{ "source": "wisprflow", "list": "meetings" }:
the model tool's schema has nolist, so an agent sees no list. It calls the existingsearch_meetingsread, 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.meetingsstays the events
source and is not renamed, and no write is declared.
Changed
- Source contract
@we-the-rebel-alliance/source-contractv0.3.0 (was v0.2.0), a devDependency bundled intodist/
(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'skind,sectionsorparts), 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 answersgap: { 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
accessvalue 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_meetingsonce 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 withACCOUNT_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 agap(expired) once and lists from 29 days ago. A minute Wispr Flow caps (more than 1000 meetings) answers agap(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_meetingsreturned 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 onfailed[]is not applicable, with its reason in the report: every meeting comes whole from asearch_meetingslisting and a failed call fails the whole read, so no single meeting fails on its own. - Attendee contacts are readable at every
accessvalue.get_participant_contactsis 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.0start, and status reports them as untested. - Jelly. The
accesssetting 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 updateandopencode plugin checkdo not work on one: to move to a newer release, remove the old entry and add the new tag.
v0.0.6
[0.0.6] - 2026-11-18
Changed
- 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. The supported range is unchanged
(>=2.2.3 <2.4.0), and so are the host devDependencies the checks compile against (2.2.3).
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
accessvalue 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_meetingsonce 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 withACCOUNT_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 agap(expired) once and lists from 29 days ago. A minute Wispr Flow caps (more than 1000 meetings) answers agap(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_meetingsreturned 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 onfailed[]is not applicable, with its reason in the report: every meeting comes whole from asearch_meetingslisting and a failed call fails the whole read, so no single meeting fails on its own. - Attendee contacts are readable at every
accessvalue.get_participant_contactsis 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.0start, and status reports them as untested. - Jelly. The
accesssetting 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 updateandopencode plugin checkdo not work on one: to move to a newer release, remove the old entry and add the new tag.
v0.0.5
[0.0.5] - 2026-11-17
Fixed
- For Memory: a listing no longer loses meetings that Wispr Flow's free plan hides. On the free plan, meetings older than
30 days are locked until the account upgrades, and Wispr Flow has no tool that names the plan, so a cursor or a
sincethat fell behind that window skipped those meetings with no sign. Every sign-in is now read as if it showed
only the last 30 days, with a day's margin: a read that starts more than 29 days ago answers
gap: { reason: "expired", since }on its first page,sincebeing where it started, and lists from 29 days ago.
The cursor carries that line, so the read's later pages carry no gap, however much later they are read, unless the
read pauses long enough to fall behind the real 30 days. On a paid plan,events_listno longer lists meetings older
than that either (search_meetingsstill reads them). - For Memory: a week Wispr Flow caps (more than 1000 meetings) is split and read again, so the cap loses nothing. It
used to stop withUNAVAILABLEand the next step "call events_list again with a later since", which skipped history.
A minute Wispr Flow still caps is now answered asgap: { reason: "window-truncated", since }and passed, so the
cursor always moves on. - For Memory: 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 now listed, once. Each read also looks up to a week behind the cursor, and the
cursor carries a short tag of each meeting it already listed or refused there (48, a few more when meetings share a
start), so a meeting there without a tag is listed and none is listed twice. A cursor of 0.0.4 still reads, and lists
nothing again. A meeting you delete before it is listed is never listed, and one already listed is not withdrawn.
Changed
- The source contract is
@we-the-rebel-alliance/source-contractv0.2.0 (#v0.2.0, 88bdc1e), bundled into
dist/index.jsas before, so the package still has no runtime dependency. The declaration andprobe's answer are
unchanged, and a page's only new key isgap, which contract 1 already has. This release declares and sends none of
the keys a consumer on 0.1.x refuses (removals[], an owner'sverified: false,permission.identityRules,
accounts.server,permission.readsIdentity, a price'sconditionsormin, an emptypermission.identity). The
owner is OpenCode's sign-in, not a Wispr Flow identity, so it is unverified; a page andprobewill say so with
verified: falseonce Memory and jelly are on 0.2.0. - The conformance report is complete and ok. The kit's expired-cursor and gap checks run on a cursor older than the
29-day line. Only the check onfailed[]is declared not applicable (atomicPages), with its reason in the
report, now exact:events_listmakes no call per meeting, and a failedsearch_meetingscall fails the whole read.
The report names the contract version it ran from. - Releases use the family's release kit r4.1 (gws
1f452e5):npm run conformance(bun test ./test/conformance)
writesreports/conformance-report.json, the release runs it again on the parent in its own job and stops unless the
report is ok for the version, and the report becomes the Release assetconformance-report.json, listed in
SHA256SUMS.docs/jelly.mdcarries jelly's shared rules, word for word. - CI's concurrency group names the event (
ci-<event>-<ref>), so a run by hand never replaces a pending push run. - Tested on OpenCode 2.2.3, 2.2.4, 2.2.5, 2.2.6, 2.2.7 and 2.3.0 (
TESTED_HOSTS, unchanged); the supported range is
still>=2.2.3 <2.4.0.
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
accessvalue 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_meetingsonce 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 withACCOUNT_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 agap(expired) once and lists from 29 days ago. A minute Wispr Flow caps (more than 1000 meetings) answers agap(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_meetingsreturned 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 onfailed[]is not applicable, with its reason in the report: every meeting comes whole from asearch_meetingslisting and a failed call fails the whole read, so no single meeting fails on its own. - Attendee contacts are readable at every
accessvalue.get_participant_contactsis 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 and 2.3.0. Other releases inside
>=2.2.3 <2.4.0start, and status reports them as untested. - Jelly. The
accesssetting 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 updateandopencode plugin checkdo not work on one: to move to a newer release, remove the old entry and add the new tag.
v0.0.4
[0.0.4] - 2026-11-15
Changed
- Admits OpenCode 2.3: the supported range is
>=2.2.3 <2.4.0(opencode.hostinpackage.jsonandSUPPORTED_HOST).
The plugin is tested on 2.2.3, 2.2.4, 2.2.5, 2.2.6, 2.2.7 and 2.3.0:TESTED_HOSTSinsrc/constants.tsis that list,
and the host and pack stages install every release in it, so CI now runs OpenCode 2.2.7 and 2.3.0 too. The
out-of-range example in the docs and tests is now 2.4.0. - What OpenCode 2.3 changes does not reach this plugin: it runs no subagents and does not subscribe to
session.tool.failed(it listens only for integration, MCP and credential events), and it has no use for the new
session.forkhook.events_listhands the tool's signal to Wispr Flow'ssearch_meetings, so it already stops
when the person presses Stop. - The icon is now Wispr Flow's own mark, Wispr Flow's five-bar symbol, the dark symbol of Wispr Flow's logo kit, in place of the family's drawn mark;
opencode.vendor.markistrue, and the README says Wispr Flow is a trademark of Wispr AI, Inc.
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
accessvalue 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_meetingsonce per page of 200 meetings of each week. 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 withACCOUNT_MISMATCH, and a consumer starts again. A cursor never expires, and Wispr Flow gives no sign of history it no longer serves, so a listing never reports a gap. - 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_meetingsreturned when last checked; their content is made up, not live-verified. Its report is incomplete on one check, the expired cursor, because the source never answersCURSOR_EXPIRED. - Attendee contacts are readable at every
accessvalue.get_participant_contactsis 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 and 2.3.0. Other releases inside
>=2.2.3 <2.4.0start, and status reports them as untested. - Jelly. The
accesssetting 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 updateandopencode plugin checkdo not work on one: to move to a newer release, remove the old entry and add the new tag.
v0.0.3
[0.0.3] - 2026-11-15
Added
- Wispr Flow's meetings as a source under the shared source contract,
@we-the-rebel-alliance/source-contract
v0.1.0:package.json's new top-levelsourceskey declareswisprflow.meetings, aneventssource of kind
meetingread withevents_list(inputsourcewisprflow), private,cost.class: "free",maxBytes65,536, with
exactly the Wispr Flow tool its read calls as its operation (search_meetings), the tools RPC
wisprflow.meetings.toolsand the probe actionwisprflow_probe. It declares no identity operation: Wispr Flow has
no tool that names the account, and the contract's schema does not yet take an empty list. Memory and jelly read the
declaration from the installed package, with the contract'sdescriptor. - For Memory and jelly: the tools RPC method
probe(actionwisprflow_probe, allowed by the default rules at every
access) answers{ source, account: "default", owner, trust }, the owner being OpenCode's sign-in exactly as every
page names it. It calls Wispr Flow for nothing, and refuses another account withACCOUNT_MISMATCH. - A page also carries
plugin,asOfandrefused[]: a meeting whose title or summary holds a secret is refused for
good withreason: "secret", and the cursor moves past it. npm run checkruns the contract's conformance kit over the declared source (the newconformancestage, in CI
too), on a synthetic Wispr Flow with no Wispr Flow call, and writesreports/conformance-report.json(git-ignored,
the same bytes every run) for a release to attach. Every check that applies passes. The report stays incomplete on
the kit's expired-cursor check: a cursor is a meeting's start and id, which never expire, and Wispr Flow gives no sign
of history it no longer serves, so the source never answersCURSOR_EXPIRED.
Changed
- For Memory, required input: a call with a
cursornamesaccount(default, asprobeanswers it); without it
the call is refused withINPUT_INVALID. A first listing may still leaveaccountout. - For Memory, the owner is unverified (OpenCode's sign-in, not a Wispr Flow identity), and its id is now always
wisprflow:credential:and the credential's id, also when the sign-in's label is an email (it wasmailto:and the
label then). The label is the owner's label, for display only: a label does not identify a connection and can be
renamed, and renaming it no longer changes the owner or breaks a cursor. Every new sign-in changes the owner, so its
cursors restart (ACCOUNT_MISMATCH: callprobe, then start again). This is also what$meresolves to. - For Memory, a cursor restart: the cursor is the contract's bound cursor (plugin
wisprflow, sourcewisprflow,
accountdefault). A cursor an earlier version issued is refused withCURSOR_INVALID; start again withsince. A
cursor from another sign-in is nowACCOUNT_MISMATCH(wasEVENTS_CURSOR_INVALID), before any read: callprobe,
then start again. The account (default) is unchanged. - The error codes of
events_listare the source contract's:INPUT_INVALID,CURSOR_INVALID,ACCOUNT_MISMATCH,
SOURCE_UNKNOWN,NEEDS_SIGN_IN(no sign-in to name as the owner) andUNAVAILABLE(the server cannot be called,
or Wispr Flow's own failure) replaceEVENTS_INVALID_INPUT,EVENTS_CURSOR_INVALID,EVENTS_ACCOUNT_UNKNOWN,
EVENTS_SOURCE_UNKNOWN,EVENTS_OWNER_UNKNOWN,EVENTS_UNAVAILABLEandEVENTS_READ_FAILED. - A page holds at most 64 KiB of JSON (the contract's default and the host's RPC cap), instead of 900,000 bytes.
- The tools RPC and the events contract are the source contract's, bundled into
dist/index.jsfrom the pinned tag;
src/host/tools-rpc.tsandsrc/host/events-list.tsare deleted, and so are theircheck-copiespins. Wispr Flow's
part of the RPC issrc/tools-rpc.ts. The RPC idwisprflow.meetings.tools, its methods and their answers are
unchanged apart fromevents_list's above, andprobeis new. - For jelly: the declared tools, sign-in and settings are unchanged;
probeis a tools RPC method, not a tool, so it
is not injelly.tools, and the default rules gainwisprflow_probe(allow) at everyaccess. Jelly does not see
the source yet: its broker on master readssourceswith its own check (backend/host/src/sources/contract.ts,
readItem), which drops an item whosepermission.eventsis not dotted, such aswisprflow_events_list, the
contract's form for an MCP-backed source. Jelly seeswisprflow.meetingsonce it reads declarations through the
source contract package (descriptor).
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
accessvalue 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_meetingsonce per page of 200 meetings of each week. 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 withACCOUNT_MISMATCH, and a consumer starts again. A cursor never expires, and Wispr Flow gives no sign of history it no longer serves, so a listing never reports a gap. - 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_meetingsreturned when last checked; their content is made up, not live-verified. Its report is incomplete on one check, the expired cursor, because the source never answersCURSOR_EXPIRED. - Attendee contacts are readable at every
accessvalue.get_participant_contactsis 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 and 2.2.6. Other releases inside
>=2.2.3 <2.3.0start, and status reports them as untested. - Jelly. The
accesssetting 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 updateandopencode plugin checkdo not work on one: to move to a newer release, remove the old entry and add the new tag.
v0.0.2
[0.0.2] - 2026-11-14
Changed
- Jelly: the declared
get_participant_contactscarries a note that Wispr Flow serves it only to accounts with Wispr
Contacts, and what it reads. Wispr Flow's live tool list of 14 November serves it, so it stays declared, read-only. docs/jelly.mdsays that signing in again from Jelly's card starts Memory's Wispr Flow source over only when the
sign-in's label is not an email, because the owner comes from the sign-in.package.jsonis"private": true, so nothing can be published to npm; an install from the release tag is
unaffected. It is kept in its canonical form, which the kit tests check innpm run check.- The release kit's plan, build and release scripts check the package's
"private": trueand canonical form, and a
buildscript is added topackage.json.
Added
test/fixtures/live-tools.json, Wispr Flow's tool list for a signed-in user with Wispr Contacts, captured live on 14
November 2026, and a test that fails when the declaration and that list disagree.
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
accessvalue you set. - Attendee contacts are readable at every
accessvalue.get_participant_contactsis 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 and 2.2.6. Other releases inside
>=2.2.3 <2.3.0start, and status reports them as untested. - Jelly. The
accesssetting 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 updateandopencode plugin checkdo not work on one: to move to a newer release, remove the old entry and add the new tag.
v0.0.1
[0.0.1] - 2026-11-13
Added
- The
jellysettings declare their choices:accessoffers Jelly's three choices, Allowed, Ask before changes and Read only, withallstill the default (needs a jelly that includes app#1301).
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
accessvalue you set. - Attendee contacts are readable at every
accessvalue.get_participant_contactsis 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 and 2.2.6. Other releases inside
>=2.2.3 <2.3.0start, and status reports them as untested. - Jelly. The
accesssetting 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 updateandopencode plugin checkdo not work on one: to move to a newer release, remove the old entry and add the new tag.
v0.0.0
[0.0.0] - 2026-11-10
Added
access, the plugin option every OpenCode plugin of this family has:"all"(the default),"ask-changes"and
"read-only". It generates the default permission block from the tool classes, and/wisprflow-statusshows it in
theAccessrow.assets/icon-128.pngandassets/icon-256.png, withopencode.iconsandopencode.vendorinpackage.json, and
scripts/check-icons.mjs, the family icon contract's check.
Changed
-
Each Wispr Flow skill's first line says how to sign in when the tools are absent:
/connect, or on Jellyjelly_connection_request. -
Every Wispr Flow tool is allowed by default. The plugin's generated block allows every known tool and the
wisprflow_*namespace, so a tool Wispr Flow adds later runs without a prompt too;get_participant_contactsis no
longer an ask. Restrict it withaccess, with an agent's own rules, or with a rule per tool; the README's
Permissions section and SECURITY say what an all-allow default means here. -
docs/scripting.mdis the family's scripting contract: the strict envelope, the location section and its unload
note, the result wording, and the refusal table, with an example-parsing test that fails when a doc example names a
method that does not exist, omits the location header, or uses a field the tool does not take. -
The CI has an
actionlintjob, andnpm run checkrunsactionlintand the icon check. -
The docs' tested-host sentences are checked against
TESTED_HOSTS, and the README prints the default block in full. -
tools RPC v2.1: every known tool is scriptable under a prior explicit allow.
wisprflow.meetings.toolsnow has one
method per known tool, by exact name and with its class (allread),get_participant_contactsincluded, which the
default block allows like every other tool. The rule is resolved before dispatch: only an
allowruns, and anaskis refused with no prompt and no tool call.describereports each method's class, a
session's permission and any live tool the table does not classify. A saved "Always allow" approval no longer
authorizes an ad-hoc script.opencode apicallers must send-H "x-opencode-directory:$PWD".
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
accessvalue you set. - Attendee contacts are readable at every
accessvalue.get_participant_contactsis 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 and 2.2.6. Other releases inside
>=2.2.3 <2.3.0start, and status reports them as untested. - Updates are not automatic for a Git install, and
opencode plugin updateandopencode plugin checkdo not work on one: to move to a newer release, remove the old entry and add the new tag.