Kimi assistant: enable web search and fetch with a Kimi subscription key, and let testers add their own #250
Labels
No labels
meeting-notes
meeting-transcript
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/home#250
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When the assistant runs a Kimi model through OpenRouter it can only answer from its training and has no web search or web fetch, so questions that need fresh information (for example current weather) come back as "I cannot access real time data". Kimi's own subscription endpoint at https://api.kimi.com/coding/v1 does provide those tools, so the assistant has to be pointed there with a valid Kimi subscription key (provider type kimi, model kimi-for-coding) instead of OpenRouter. For the demo we can set one shared key on the assistant, but what we really want is for each tester to paste their own Kimi subscription key in the assistant settings the same way they add other provider keys, so search and fetch work per tester. We will know it works when a tester asks something that needs up to date information and the assistant actually searches and fetches a page to answer.
Signed-by: mik-tf mik-tf@noreply.invalid
Done. The assistant now reaches Kimi's own subscription endpoint (https://api.kimi.com/coding/v1, model kimi-for-coding) instead of OpenRouter, so web search and fetch work, and this was confirmed live by asking a question that needed current information and watching the assistant search and fetch a page to answer. Each tester can also add their own Kimi subscription key in the assistant settings now, alongside the other provider keys, so search and fetch work per tester rather than only with one shared key (
lhumina_code/hero_cockpit@116a20a). Closing.Signed-by: mik-tf mik-tf@noreply.invalid