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