Skip to content

Releases

v0.0.7

Choose a tag to compare

@github-actions github-actions released this 20 Nov 13:07
131e226

[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 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.

v0.0.6

Choose a tag to compare

@github-actions github-actions released this 18 Nov 15:13
d75384c

[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 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.

v0.0.5

Choose a tag to compare

@github-actions github-actions released this 17 Nov 17:57
7426ec6

[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
    since that 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, since being 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_list no longer lists meetings older
    than that either (search_meetings still 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 with UNAVAILABLE and the next step "call events_list again with a later since", which skipped history.
    A minute Wispr Flow still caps is now answered as gap: { 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-contract v0.2.0 (#v0.2.0, 88bdc1e), bundled into
    dist/index.js as before, so the package still has no runtime dependency. The declaration and probe's answer are
    unchanged, and a page's only new key is gap, which contract 1 already has. This release declares and sends none of
    the keys a consumer on 0.1.x refuses (removals[], an owner's verified: false, permission.identityRules,
    accounts.server, permission.readsIdentity, a price's conditions or min, an empty permission.identity). The
    owner is OpenCode's sign-in, not a Wispr Flow identity, so it is unverified; a page and probe will say so with
    verified: false once 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 on failed[] is declared not applicable (atomicPages), with its reason in the
    report, now exact: events_list makes no call per meeting, and a failed search_meetings call 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)
    writes reports/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 asset conformance-report.json, listed in
    SHA256SUMS. docs/jelly.md carries 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 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 and 2.3.0. 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.

v0.0.4

Choose a tag to compare

@github-actions github-actions released this 15 Nov 16:06
e13d9b5

[0.0.4] - 2026-11-15

Changed

  • Admits OpenCode 2.3: the supported range is >=2.2.3 <2.4.0 (opencode.host in package.json and SUPPORTED_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_HOSTS in src/constants.ts is 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.fork hook. events_list hands the tool's signal to Wispr Flow's search_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.mark is true, 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 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. 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. 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_meetings returned 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 answers CURSOR_EXPIRED.
  • 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 and 2.3.0. 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.

v0.0.3

Choose a tag to compare

@github-actions github-actions released this 15 Nov 03:16
7a60252

[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-level sources key declares wisprflow.meetings, an events source of kind
    meeting read with events_list (input source wisprflow), private, cost.class: "free", maxBytes 65,536, with
    exactly the Wispr Flow tool its read calls as its operation (search_meetings), the tools RPC
    wisprflow.meetings.tools and the probe action wisprflow_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's descriptor.
  • For Memory and jelly: the tools RPC method probe (action wisprflow_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 with ACCOUNT_MISMATCH.
  • A page also carries plugin, asOf and refused[]: a meeting whose title or summary holds a secret is refused for
    good with reason: "secret", and the cursor moves past it.
  • npm run check runs the contract's conformance kit over the declared source (the new conformance stage, in CI
    too), on a synthetic Wispr Flow with no Wispr Flow call, and writes reports/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 answers CURSOR_EXPIRED.

Changed

  • For Memory, required input: a call with a cursor names account (default, as probe answers it); without it
    the call is refused with INPUT_INVALID. A first listing may still leave account out.
  • 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 was mailto: 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: call probe, then start again). This is also what $me resolves to.
  • For Memory, a cursor restart: the cursor is the contract's bound cursor (plugin wisprflow, source wisprflow,
    account default). A cursor an earlier version issued is refused with CURSOR_INVALID; start again with since. A
    cursor from another sign-in is now ACCOUNT_MISMATCH (was EVENTS_CURSOR_INVALID), before any read: call probe,
    then start again. The account (default) is unchanged.
  • The error codes of events_list are the source contract's: INPUT_INVALID, CURSOR_INVALID, ACCOUNT_MISMATCH,
    SOURCE_UNKNOWN, NEEDS_SIGN_IN (no sign-in to name as the owner) and UNAVAILABLE (the server cannot be called,
    or Wispr Flow's own failure) replace EVENTS_INVALID_INPUT, EVENTS_CURSOR_INVALID, EVENTS_ACCOUNT_UNKNOWN,
    EVENTS_SOURCE_UNKNOWN, EVENTS_OWNER_UNKNOWN, EVENTS_UNAVAILABLE and EVENTS_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.js from the pinned tag;
    src/host/tools-rpc.ts and src/host/events-list.ts are deleted, and so are their check-copies pins. Wispr Flow's
    part of the RPC is src/tools-rpc.ts. The RPC id wisprflow.meetings.tools, its methods and their answers are
    unchanged apart from events_list's above, and probe is new.
  • For jelly: the declared tools, sign-in and settings are unchanged; probe is a tools RPC method, not a tool, so it
    is not in jelly.tools, and the default rules gain wisprflow_probe (allow) at every access. Jelly does not see
    the source yet: its broker on master reads sources with its own check (backend/host/src/sources/contract.ts,
    readItem), which drops an item whose permission.events is not dotted, such as wisprflow_events_list, the
    contract's form for an MCP-backed source. Jelly sees wisprflow.meetings once 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 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. 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. 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_meetings returned 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 answers CURSOR_EXPIRED.
  • 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 and 2.2.6. Other releases inside >=2.2.3 <2.3.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.

v0.0.2

Choose a tag to compare

@github-actions github-actions released this 14 Nov 20:45
e915d71

[0.0.2] - 2026-11-14

Changed

  • Jelly: the declared get_participant_contacts carries 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.md says 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.json is "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 in npm run check.
  • The release kit's plan, build and release scripts check the package's "private": true and canonical form, and a
    build script is added to package.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 access value you set.
  • 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 and 2.2.6. Other releases inside >=2.2.3 <2.3.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.

v0.0.1

Choose a tag to compare

@github-actions github-actions released this 13 Nov 16:50
6eb9023

[0.0.1] - 2026-11-13

Added

  • The jelly settings declare their choices: access offers Jelly's three choices, Allowed, Ask before changes and Read only, with all still 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 access value you set.
  • 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 and 2.2.6. Other releases inside >=2.2.3 <2.3.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.

v0.0.0

Choose a tag to compare

@github-actions github-actions released this 11 Nov 13:15
v0.0.0
d6122f5

[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-status shows it in
    the Access row.
  • assets/icon-128.png and assets/icon-256.png, with opencode.icons and opencode.vendor in package.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 Jelly jelly_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_contacts is no
    longer an ask. Restrict it with access, 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.md is 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 actionlint job, and npm run check runs actionlint and 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.tools now has one
    method per known tool, by exact name and with its class (all read), get_participant_contacts included, which the
    default block allows like every other tool. The rule is resolved before dispatch: only an
    allow runs, and an ask is refused with no prompt and no tool call. describe reports 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 api callers 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 access value you set.
  • 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 and 2.2.6. Other releases inside >=2.2.3 <2.3.0 start, and status reports them as untested.
  • 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.