@joe-broadhead/opencode-plaud 0.0.2 → 0.0.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -2,6 +2,21 @@
2
2
 
3
3
  All notable changes to this project are documented here. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and versions follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
4
4
 
5
+ ## [0.0.4] - 2026-11-04
6
+
7
+ ### Added
8
+
9
+ - Jelly shows the plugin's one-line summary and icon: `jelly.summary`, and `jelly.icon`, shipped as `assets/icon.svg`.
10
+ - Scripts can call `plaud_recent` through the tools RPC, as the method `recent`. Its input is `{ "limit"?: 1 to 20 }`; the account is the envelope's `account`, as for the five reads, and an account the options don't name is `ACCOUNT_UNKNOWN`. It runs under the same rules as for the model: `plaud_recent`, then the account's `list_files`, and a refused read is `PERMISSION_DENIED` naming that read. An input it does not take, such as `account`, is the new code `INPUT_INVALID`. `describe` lists it.
11
+
12
+ ## [0.0.3] - 2026-11-04
13
+
14
+ ### Added
15
+
16
+ - `plaud_recent` (`tools.plaud.recent` in Code Mode): the newest recordings, one line each, with the title, the start time in UTC and the length. It takes an optional `account` and `limit` (1 to 20, 8 by default), and reads through the account's own `list_files`. It runs without asking: the default rules allow `plaud_recent` by its exact name, and a rule for the account's `list_files` applies to it too. Because it is one tool for every account, a rule can name the account as its resource, such as `{ "action": "plaud_recent", "resource": "work", "effect": "deny" }`. It is not a tools RPC method; a script reads `list_files`.
17
+ - `/plaud-status` counts `plaud_recent` as one of the plugin's own tools, not as an unknown Plaud tool. The block it shows for agents defined in your config has the `plaud_recent` rule; copy it again into those agents.
18
+ - A `jelly` section in `package.json`, for [Jelly](https://heyjelly.ai): the plugin's title, each tool with its permission, its default effect and whether it only reads, the skills, the `plaud*` sign-in, which folds every account into one row, and a Home feed preset, "Recent Plaud recordings", that shows `plaud_recent` every 30 minutes. Jelly reads it without loading the plugin. `docs/jelly.md` explains it.
19
+
5
20
  ## [0.0.2] - 2026-11-04
6
21
 
7
22
  ### Added
package/README.md CHANGED
@@ -47,6 +47,7 @@ Ask about your recordings, for example "what did I record this week?" or "save t
47
47
  | `plaud_get_transcript` | `tools.plaud.get_transcript` | One transcript block, a page at a time | runs |
48
48
  | `plaud_get_file` | `tools.plaud.get_file` | One recording in full, often over 100 KB; the skill and Code Mode's description send the model to the notes or the transcript first | runs |
49
49
  | `plaud_get_current_user` | `tools.plaud.get_current_user` | The signed-in account | runs |
50
+ | `plaud_recent` | `tools.plaud.recent` | The newest recordings, one line each: title, start time and length | runs |
50
51
  | `plaud_export` | `tools.plaud.export` | Save audio, a transcript or a note as a file | asks |
51
52
 
52
53
  Plaud maintains the read tools and their arguments. Plaud has no write API: nothing here can create, rename, delete, upload, share or send a recording. Any other tool on a Plaud server asks before it runs.
@@ -80,7 +81,7 @@ See [SECURITY.md](https://github.com/joe-broadhead/opencode-plaud/blob/HEAD/SECU
80
81
 
81
82
  ### Scripts
82
83
 
83
- A script or a cron job can call Plaud's five read tools with no model, through `opencode api`. It runs as a session and its agent, under that agent's permission rules and the session's own. Add `"account": "<alias>"` to read another account. Exports and every other Plaud tool are never available to scripts, and a script never gets a signed link:
84
+ A script or a cron job can call Plaud's five read tools and `plaud_recent` with no model, through `opencode api`. It runs as a session and its agent, under that agent's permission rules and the session's own. Add `"account": "<alias>"` to read another account. Exports and every other Plaud tool are never available to scripts, and a script never gets a signed link:
84
85
 
85
86
  ```sh
86
87
  opencode api post /api/rpc/plaud.recordings.tools/list_files \
@@ -91,7 +92,7 @@ See [Scripting](https://github.com/joe-broadhead/opencode-plaud/blob/HEAD/docs/s
91
92
 
92
93
  ## Permissions
93
94
 
94
- The plugin adds default rules to each agent: Plaud's read tools run without a prompt, and `plaud_export` and any other Plaud tool ask first. "Always allow" on an export remembers only that account and kind, such as `default:transcript`. Your own `permissions` rules win over the defaults.
95
+ The plugin adds default rules to each agent: Plaud's read tools and `plaud_recent` run without a prompt, and `plaud_export` and any other Plaud tool ask first. "Always allow" on an export remembers only that account and kind, such as `default:transcript`. Your own `permissions` rules win over the defaults.
95
96
 
96
97
  `opencode run` and other runs where nobody can answer refuse an export unless a rule allows it. To export without a prompt, or to block some exports, see [Permissions](https://github.com/joe-broadhead/opencode-plaud/blob/HEAD/docs/configuration.md#permissions).
97
98
 
@@ -0,0 +1 @@
1
+ <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 48 48" width="48" height="48"><rect width="48" height="48" rx="12" fill="#141414"/><g fill="none" stroke="#FFFFFF" stroke-width="3.5" stroke-linecap="round"><path d="M12 21v6"/><path d="M18 16v16"/><path d="M24 11v26"/><path d="M30 17v14"/><path d="M36 21v6"/></g></svg>