Replace opencode source links with Kilo URLs#8855
Replace opencode source links with Kilo URLs#8855kilo-code-bot[bot] wants to merge 1 commit intomainfrom
Conversation
|
I don't think this is mergeable, but these are indicative of todos |
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
|
|
||
| if (provider === "opencode") { | ||
| prompts.log.info("Create an api key at https://opencode.ai/auth") | ||
| prompts.log.info("Create an api key at https://kilo.ai/gateway") // kilocode_change |
There was a problem hiding this comment.
WARNING: opencode still points at the OpenCode Zen backend
This help text now sends users to kilo.ai/gateway, but the opencode provider still resolves through the opencode.ai/zen/v1 model metadata and uses OPENCODE_API_KEY. That mismatch can make users store a Kilo Gateway key under the opencode provider and then fail authentication against the OpenCode endpoint.
| "With a single API key you'll get access to models such as Claude, GPT, Gemini, GLM and more.", | ||
| "provider.connect.opencodeZen.visit.prefix": "Visit ", | ||
| "provider.connect.opencodeZen.visit.link": "https://opencode.ai/zen", | ||
| "provider.connect.opencodeZen.visit.link": "https://kilo.ai/gateway", |
There was a problem hiding this comment.
WARNING: This copy change is currently unused in the VS Code flow
The extension's provider connect dialog does not read provider.connect.opencodeZen.*; it only renders the generic API-key description path. As written, these locale updates will not actually change the VS Code provider UX that the PR description calls out.
Code Review SummaryStatus: 2 Issues Found | Recommendation: Address before merge Overview
Fix these issues in Kilo Cloud Issue Details (click to expand)WARNING
Other Observations (not in diff)No additional out-of-diff issues. Files Reviewed (26 files)
Reviewed by gpt-5.4-20260305 · 24,915,687 tokens |
1 participant
Update source-extracted user-facing URLs from OpenCode and legacy domains to Kilo-owned destinations across the CLI, VS Code provider copy, and source link index.
Remove the upstream TUI schema reference from migrated TUI config output until Kilo publishes an equivalent schema, keeping generated source links Kilo-branded.