feat(tui): add Kimi WebBridge install entry to /plugins panel#1494
Conversation
Surface a hardcoded Kimi WebBridge entry at the top of the Official tab in the /plugins panel. Selecting it opens the WebBridge install page in the user's browser instead of going through the plugin install flow, since WebBridge is a browser extension plus local daemon rather than an installable plugin package.
🦋 Changeset detectedLatest commit: c862c19 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d0182725b0
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| if (isWebBridgeEntry(entry)) { | ||
| this.opts.onSelect({ kind: 'open-url', url: WEB_BRIDGE_URL, label: entry.displayName }); |
There was a problem hiding this comment.
When a custom or curated marketplace contains an entry whose id is kimi-webbridge, it lands on the Third-party tab because thirdPartyEntries includes every non-official entry, but this id-only check routes Enter to open-url instead of the normal install selection. That makes such marketplace entries impossible to install or update from the panel; the special case should apply only to the hardcoded pinned WEB_BRIDGE_ENTRY rather than every catalog entry with the same id.
Useful? React with 👍 / 👎.
Match the hardcoded pinned WebBridge entry by object reference instead of by id. A curated or custom marketplace entry on the Third-party tab can legitimately reuse the kimi-webbridge id; routing by id hijacked Enter on those rows and opened the WebBridge page instead of installing. The Official tab still dedupes a same-id official catalog entry so the pinned row is not duplicated.
|
Codex Review: Didn't find any major issues. Nice work! Reviewed commit: ℹ️ About Codex in GitHubCodex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback". |
The previous "webpage" status did not make it clear that selecting this row opens an external page rather than installing in-app. "open in browser" states the action directly and contrasts with the install label on regular plugin rows.
…tests Two message-flow tests pressed Enter on the Official tab assuming index 0 was the Kimi Datasource entry. The hardcoded Kimi WebBridge row now leads that tab, so move down one row before installing.
1 participant
Related Issue
No linked issue — this was requested directly. The motivation is described in the next section.
Problem
Kimi WebBridge — the browser extension plus local daemon that lets Kimi Code drive the user's real browser — has no entry point inside the TUI. Users who do not already know it exists have no way to discover or install it from the CLI. The
/pluginspanel is the natural place to surface it.What changed
/pluginspanel, even when the marketplace catalog is still loading or fails to load.Checklist
gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.