v0.0.0

[0.0.0] - 2026-11-11

Added

• The access option restricts what the generated default rules allow: "all" (the default), "ask-changes" and "read-only". The block is generated from the tool classes, with the plaud*_* namespace rule first, so a tool Plaud adds later follows the same value. /plaud-status and the status RPC report the value and the block.

Changed

• Each skill explains how to connect Plaud when its tools are absent, including additional accounts.
• Every tool is allowed by default. The plugin inserts an allow for each tool it registers and for the plaud*_* namespace: the five reads of every account's server, plaud_recent, plaud_events_list, and plaud_export, which writes a file. An agent runs them without asking, and nothing is held back. "ask-changes" makes every export ask, and "read-only" denies exports and any tool the plugin does not know; the reads always run.
• An export folder is outside the project, so OpenCode also checks external_directory on the folder, as well as plaud_export. A refusal that names it is EXPORT_PATH_NOT_PERMITTED, whose next step is the rule to allow, and a script that exports outside the project needs both rules. README, SECURITY, docs/configuration.md and docs/scripting.md say so.
• The tools RPC follows the same default: every method is allowed unless access or the session's rules restrict it.
• The tools RPC is v2: every known read is a method with its class, plus plaud_recent (method recent) and plaud_events_list (method events_list), and a call runs only with a prior explicit allow in the agent's or the session's rules. An ask is refused before the tool runs, so no prompt waits, and a saved "Always allow" does not authorize an ad-hoc script. plaud_export writes a file and stays a direct tool: no script can call it. Signed links stay withheld on the script path.

Known limits

• Platforms. macOS and Linux only. Windows is not tested.
• Region. Plaud's server is in the US. Accounts in other regions are untested; set url if Plaud gives you another address.
• Read-only against Plaud. Plaud has no write API, so nothing here creates, renames, deletes, uploads, shares or sends a recording.
• New Plaud tools. A tool Plaud adds later follows access, so it runs at the default "all". It is not a script method until a plugin release.
• Signed links. Tool results never show a signed link. Audio and transcripts reach a file only through plaud_export.
• Unattended exports. An export folder is outside the project, so an unattended run needs the external_directory rule as well as plaud_export (see Permissions).
• Tested hosts. Tested on OpenCode 2.2.3, 2.2.4, 2.2.5 and 2.2.6. A later 2.2 release starts, and /plaud-status marks it 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.