docs: document Kimi Code login and no-logout setup - #443
Open
omnigent-ci[bot] wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
omnigent-ci
Bot
added
automated-docs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation update for omnigent-ai/omnigent#3292 — Fix Kimi harness login detection and remove broken logout
Changes documented
app/docs/build/harnesses/page.mdx— added a "Kimi Code" section covering the curl install +kimi login(Moonshot OAuth or API key), the~/.kimi-code/credentials/kimi-code.jsoncredential file that drivesomni setup's "Signed in" vs "Not configured" state, and the fact that Kimi has nokimi logoutsubcommand (sign out by deleting the credential file).Manual review needed
Source PR: omnigent-ai/omnigent#3292 · merged by @dhruv0811
Drafted automatically by the doc-sync workflow. Review for accuracy before merging.