Skip to content

Fix enabled optional providers in channel runtime picker - #186

Merged
makeitfutureDev merged 1 commit into
betafrom
fix/channel-engine-picker-oct17
Oct 16, 2026
Merged

makeitfutureDev merged 1 commit into
betafrom
fix/channel-engine-picker-oct17

Conversation

@makeitfutureDev

Copy link
Copy Markdown
Owner

The admin channel Runtime picker only offered Default, Claude and Codex, so enabled optional providers could not be selected and an existing provider pin could render as Default. Populate it from the same enabled adapter manifest used by the global and DM editors, preserving the saved engine/model on unrelated saves.

Validation: a real browser regression failed against beta's original dropdown, then passed with both optional providers, unrelated save/reload, switching providers and disabled-adapter filtering. Three targeted browser tests pass; full coverage passes (3,816 tests, 29 optional skips; the new browser case was also executed explicitly), plus static checks, security coverage, secret scan, dependency audit and DCO.

Live provider acceptance remains recorded separately: isolated admin-browser and real provider execution exposed this defect; native Slack selector branches remain incomplete. No main promotion or production provider configuration changes.

Signed-off-by: Tiberiu Socaci <tsocaci@makeitfuture.com>
@makeitfutureDev
makeitfutureDev merged commit 0172385 into beta Oct 16, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants