dotCooCoo a4a516e82f Plug-ins: only a person can approve a plug-in's permissions and heavy budget ...

`plugin.install` accepted `grant` and `allowHeavy` from any client, so
the program installing a plug-in could answer its own permission
prompt.

The desktop app now shows an approval dialog that names the module,
its hash and what it asks for. Confirming it gives the engine a
one-use approval tied to that module id, hash and permission list. A
control or MCP request and a frame of synthetic input cannot confirm
the dialog, and Enter does not confirm it.

Without such an approval, `grant` and `allowHeavy` are refused. The
new `--allow-plugin-grants` flag on `mcp` and `run` lets a person who
starts a headless session accept them from requests. The flag cannot
be combined with `--connect`. A module already approved in the desktop
app still installs through its stored grant.

2026-11-08 11:03:38 -08:00

..

examples

Render: a long dashed stroke is outlined only near the view after an edit

2026-11-05 03:55:48 +07:00

src

Plug-ins: only a person can approve a plug-in's permissions and heavy budget

2026-11-08 11:03:38 -08:00

tests

Plug-ins: only a person can approve a plug-in's permissions and heavy budget

2026-11-08 11:03:38 -08:00

Cargo.toml

File formats: HEIC and HEIF images open and place

2026-11-08 23:51:41 +07:00