Mohamed Boudra 389db81784 feat(plugin): provider plugins declare option controls and receive option changes ...

A provider plugin reports `controls` and the `providerOptions` it runs in
`session.config`, and receives running-session changes as
`session.configure` `changes.providerOptions` (null returns a key to its
default), under the same apply-or-throw contract as built-in providers.
A control may declare a `defaultValue`; a value a plugin reports at that
default for a key nobody set stays unset instead of being pinned to the agent.

A plugin that still reports `settings` keeps working: the daemon reads each
setting as a control plus an option and sends changes in both shapes
(COMPAT(plugin-provider-settings)).

The app resolves a control's icon as a Lucide name when it is not one of the
built-in kebab-case names, so a plugin's icon shows live and in drafts.
Public docs and the provider-direct example use only `providerOptions` and
controls; the migration doc gains the rows.

2026-11-02 00:29:50 +01:00

..

src

feat(plugin): provider plugins declare option controls and receive option changes

2026-11-02 00:29:50 +01:00

package.json

chore(release): reconcile 0.15.0-beta.1 metadata (#8443)

2026-11-01 12:56:41 +07:00

tsconfig.examples.json

Translate plugin content and labels in each app language (#7478)

2026-10-21 13:40:46 +07:00

tsconfig.json

Let plugins provide coding agents (#4314)

2026-09-04 19:56:57 +02:00