Ettore Di Giacinto 7ce4507da1 feat(addons): keep per-person settings that an add-on declares ...

An add-on can declare userSettings in its manifest: a key, the allowed
values and a default. The host keeps each person's answer in the account
database every frontend shares (one file when accounts are off), checks
every write against the declaration, and never asks the add-on.

GET and PUT /api/addons/{id}/user-settings read and write them. A write
needs the person's own browser session, so no API key, model or tool can
change one. A setting may carry a role that the host reads for its own
rules; the host fixes the values and the default of a role so a manifest
cannot loosen it. Pages reach their settings through sdk.userSettings,
which is bound to the add-on that calls it.

Assisted-by: Claude:claude-sonnet-5-5 go node

2026-11-03 22:46:22 +00:00

..

apps_test.go

refactor(addons): remove the shims for older add-on data

2026-11-03 16:56:49 +00:00

apps.go

feat(addons): keep per-person settings that an add-on declares

2026-11-03 22:46:22 +00:00

extensions_test.go

feat(addons): declare typed host capabilities (#13034)

2026-11-02 23:50:40 +00:00

installed.go

feat(addons): declare typed host capabilities (#13034)

2026-11-02 23:50:40 +00:00

modelactions_test.go

feat(addons): declare typed host capabilities (#13034)

2026-11-02 23:50:40 +00:00

resources_test.go

refactor(addons): make manifest api 2 the only version

2026-11-03 16:15:07 +00:00