From 5952f22ca21e5c4e876e571af24d85e6f2cbaf6f Mon Sep 17 00:00:00 2001
From: Jiang Bohan <bhjiang@outlook.com>
Date: Mon, 2 Feb 2026 17:10:14 +0800
Subject: [PATCH] docs: add LLM providers documentation

- Document OAuth providers (claude-code, openai-codex)
- Document API Key providers
- Add /provider command usage example
- Add OAuth login instructions
---
 README.md | 57 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 57 insertions(+)

diff --git a/README.md b/README.md
index e25d1936..5aee5c5e 100644
--- a/README.md
+++ b/README.md
@@ -95,6 +95,63 @@ Optional overrides:
 - `SMC_CREDENTIALS_PATH` — custom path for `credentials.json5`
 - `SMC_SKILLS_ENV_PATH` — custom path for `skills.env.json5`
 
+### LLM Providers
+
+Super Multica supports multiple LLM providers with two authentication methods:
+
+**OAuth Providers** (use external CLI login):
+- `claude-code` — Claude Code OAuth (requires `claude login`)
+- `openai-codex` — OpenAI Codex OAuth (requires `codex login`)
+
+**API Key Providers** (configure in `credentials.json5`):
+- `anthropic`, `openai`, `kimi-coding`, `google`, `groq`, `mistral`, `xai`, `openrouter`
+
+#### Check Provider Status
+
+```bash
+# In interactive mode
+/provider
+
+# Output shows all providers with status
+🔌 Provider Status
+
+Current: kimi-coding
+
+Available Providers:
+  ID               Name                 Auth         Status
+  ──────────────────────────────────────────────────────────────────────
+  ✓ claude-code    Claude Code (OAuth)  OAuth        ready
+  ✗ openai-codex   Codex (OAuth)        OAuth        not logged in
+  ✓ kimi-coding    Kimi Code            API Key      configured (current)
+  ...
+```
+
+#### Using OAuth Providers
+
+```bash
+# 1. Install and login to Claude Code
+npm install -g @anthropic-ai/claude-code
+claude login
+
+# 2. Start multica with claude-code provider
+multica --provider claude-code
+```
+
+#### Using API Key Providers
+
+Add your API key to `~/.super-multica/credentials.json5`:
+
+```json5
+{
+  llm: {
+    provider: "openai",
+    providers: {
+      openai: { apiKey: "sk-xxx" }
+    }
+  }
+}
+```
+
 ### Configuration Priority
 
 Each setting is resolved in order (first match wins):