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.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 sourcewisprflow), 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.