Skip to content

v0.0.5

Choose a tag to compare

@github-actions github-actions released this 17 Nov 17:57
· 11 commits to master since this release
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.