Skip to content

v0.0.4

Choose a tag to compare

@github-actions github-actions released this 15 Nov 16:06
· 21 commits to master since this release
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.