From 15f63a41e7206cbc8bd24fa787d62c6859ad5576 Mon Sep 17 00:00:00 2001
From: "omnigent-ci[bot]" <294685417+omnigent-ci[bot]@users.noreply.github.com>
Date: Tue, 4 Aug 2026 19:05:07 +0000
Subject: [PATCH] docs: document Kimi Code login and no-logout setup

---
 app/docs/build/harnesses/page.mdx | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/app/docs/build/harnesses/page.mdx b/app/docs/build/harnesses/page.mdx
index 811645e..2860cc5 100644
--- a/app/docs/build/harnesses/page.mdx
+++ b/app/docs/build/harnesses/page.mdx
@@ -72,6 +72,29 @@ curl -fsSL https://x.ai/cli/install.sh | bash
 grok login --device-auth   # xAI OAuth (device-code capable); or set XAI_API_KEY
 ```
 
+## Kimi Code
+
+Kimi Code (`kimi`, alias `kimi-code`) brings **its own auth** — Omnigent stores
+no credential. Kimi ships via a curl installer (no npm package), so install the
+CLI and sign in through it first:
+
+```
+curl -fsSL https://code.kimi.com/kimi-code/install.sh | bash
+kimi login   # Moonshot OAuth, or paste a Moonshot API key
+```
+
+`kimi login` writes its credential to `~/.kimi-code/credentials/kimi-code.json`.
+`omni setup` detects that file and shows Kimi as **Signed in** once a login has
+completed; while the CLI is installed but no credential is present it shows
+**Not configured** with a "Sign in with `kimi login`" hint.
+
+Kimi has **no** `kimi logout` subcommand, so `omni setup` offers no sign-out
+row. To sign out, delete the credential file:
+
+```
+rm ~/.kimi-code/credentials/kimi-code.json
+```
+
 ## Custom ACP agents
 
 Beyond the agents above, the generic `acp` harness drives *any* agent that