vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 16:30:57 +00:00
Code Issues Packages Projects Releases Wiki Activity

feat(plugins): surface manifest provider setup choices (#71240)

Browse Source
This commit is contained in:
Vincent Koc
2026-04-24 13:14:49 -07:00
committed by GitHub
parent 8154337cb6
commit cf858258c7
5 changed files with 189 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/plugins/architecture-internals.md
View File

@@ -71,7 +71,9 @@ or fallback behavior without changing runtime loading semantics.
Setup discovery now prefers descriptor-owned ids such as `setup.providers` and
`setup.cliBackends` to narrow candidate plugins before it falls back to
`setup-api` for plugins that still need setup-time runtime hooks. Explicit
`setup-api` for plugins that still need setup-time runtime hooks. Provider
setup flow uses manifest `providerAuthChoices` first, then falls back to
runtime wizard choices and install-catalog choices for compatibility. Explicit
`setup.requiresRuntime: false` is a descriptor-only cutoff; omitted
`requiresRuntime` keeps the legacy setup-api fallback for compatibility. If more
than one discovered plugin claims the same normalized setup provider or CLI

2
docs/plugins/manifest.md
View File

@@ -168,6 +168,8 @@ or npm install metadata. Those belong in your plugin code and `package.json`.
Each `providerAuthChoices` entry describes one onboarding or auth choice.
OpenClaw reads this before provider runtime loads.
Provider setup flow prefers these manifest choices, then falls back to runtime
wizard metadata and install-catalog choices for compatibility.
| Field | Required | Type | What it means |
| --------------------- | -------- | ----------------------------------------------- | -------------------------------------------------------------------------------------------------------- |