Skip to content

fix(web): show active wasm channels correctly in settings#2375

Open
G7CNF wants to merge 8 commits intonearai:stagingfrom
G7CNF:codex/issue-2235-extension-activation-state
Open

fix(web): show active wasm channels correctly in settings#2375
G7CNF wants to merge 8 commits intonearai:stagingfrom
G7CNF:codex/issue-2235-extension-activation-state

Conversation

@G7CNF
Copy link
Copy Markdown
Contributor

@G7CNF G7CNF commented Apr 12, 2026

Fixes #2235.\n\nCurrent runtime behavior for authenticated WASM channels is now reflected in the settings UI:\n- active + authenticated channels are shown as Active even if owner-bound metadata is not yet resolved\n- already-authenticated cards now show Reconfigure instead of Setup\n- pairing claim UI only appears when the channel is active but not owner-bound\n\nValidated with focused Rust tests and for the settings UI script.

@github-actions github-actions bot added scope: channel/web Web gateway channel scope: docs Documentation size: XL 500+ changed lines risk: medium Business logic, config, or moderate-risk modules contributor: core 20+ merged PRs labels Apr 12, 2026
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a standalone MCP stdio bridge for the gws binary, featuring command allowlisting, secret redaction, and environment isolation. It also refactors extension activation logic to prioritize runtime state, ensuring WASM channels are treated as active regardless of owner-binding metadata, and updates the web UI accordingly. Feedback suggests cleaning up the internal API by removing now-unused parameters in activation functions and refactoring duplicated extension mapping logic between the server and extension handlers to improve maintainability.

@G7CNF G7CNF force-pushed the codex/issue-2235-extension-activation-state branch from dc3d504 to 58cee3a Compare April 12, 2026 14:36
@github-actions github-actions bot added the scope: extensions Extension management label Apr 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

contributor: core 20+ merged PRs risk: medium Business logic, config, or moderate-risk modules scope: channel/web Web gateway channel scope: docs Documentation scope: extensions Extension management size: XL 500+ changed lines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[QA] Activate button shows credential popup for already-installed tools

1 participant