Support wildcard topic in mail permissions
topic: null in a permission entry now matches any topic, allowing broad grants without specifying a specific topic. set-mail-permission topic param is now optional; omitting it stores null (wildcard). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -145,7 +145,7 @@ Built-in actions:
|
||||
| `open-browser` | queue | `url` (http/https only) |
|
||||
| `open-terminal` | queue | `path` (optional, defaults to workspace) |
|
||||
| `send-email` | auto-accept | `to`, `subject`, `body`, `topic` |
|
||||
| `set-mail-permission` | auto-accept | `target_user`, `to`, `topic`, `allow` (bool) |
|
||||
| `set-mail-permission` | auto-accept | `target_user`, `to`, `allow` (bool), `topic` (optional — omit to match any topic) |
|
||||
| `get-mail-permissions` | auto-accept | `target_user` (optional) |
|
||||
|
||||
`send-email` checks that the caller has a mail permission entry matching `(caller, to, topic)` before sending. Permissions are managed via `set-mail-permission`, which requires the caller to have `canApprove` over the target user — so only humans can grant/revoke permissions for agents.
|
||||
|
||||
Reference in New Issue
Block a user