← Commit history

0.5.64 (source only, publish held): legacy pip Kimi 1.x upgraded to 2.x by the bootstrap; skill notes the 403

John Lauer ·2d2744683e · ·parent a570b08
3 files changed +25−1
install.sh+20
@@ -333,6 +333,26 @@ CLAUDEW   fi fi +# 4e. Legacy pip Kimi 1.x (AdomLapper 2026-09-20: kimi-cli 1.49.0 from Aug 31). It answers+#     every prompt with a 403 "subscription does not have access to Kimi Code" over credentials+#     the extension uses fine, and its self-upgrade kills the TUI. When it is present, install+#     Kimi 2.x the way Manage AIs does (the official installer into ~/.kimi-code/bin), point+#     ~/.local/bin/kimi at it, set the region to global, and remove the 1.x package.+KV="$(command -v kimi >/dev/null 2>&1 && kimi --version 2>/dev/null | head -1 || true)"+if [ -n "$KV" ] && ! printf '%s' "$KV" | grep -qE '(^|[^0-9.])[2-9]\.[0-9]'; then+  echo "  kimi cli: legacy $KV found; installing Kimi 2.x"+  if curl -fsSL https://code.kimi.com/kimi-code/install.sh | KIMI_NO_MODIFY_PATH=1 bash >/dev/null 2>&1 && [ -x "$HOME/.kimi-code/bin/kimi" ]; then+    rm -f "$HOME/.local/bin/kimi" "$HOME/.local/bin/kimi-legacy"+    ln -sfn "$HOME/.kimi-code/bin/kimi" "$HOME/.local/bin/kimi"+    [ -s "$HOME/.kimi-code/region" ] || printf global > "$HOME/.kimi-code/region"+    pk="$(python3 -c 'import kimi_cli,os;print(os.path.dirname(kimi_cli.__file__))' 2>/dev/null || true)"+    if [ -n "$pk" ] && [ -d "$pk" ]; then rm -rf "$pk" "$pk"-*.dist-info "$(dirname "$pk")"/kimi_cli-*.dist-info; echo "  kimi cli: removed the legacy pip package ($pk)"; fi+    echo "  kimi cli: now $("$HOME/.kimi-code/bin/kimi" --version 2>/dev/null | head -1)"+  else+    echo "  kimi cli: 2.x install failed (offline?); leaving the legacy CLI in place"+  fi+fi+ # 5. code-server config.yaml — silence code-server's own update nags. install -d -m 0755 "$HOME/.config/code-server" cat > "$HOME/.config/code-server/config.yaml" <<'CSCONF'
package.json+1−1
@@ -4,7 +4,7 @@   "type": "bootstrap",   "title": "Adom Hydrogen (platform base)",   "brief": "Layer Hydrogen's workspace onto a standard Adom workstation.",-  "version": "0.5.63",+  "version": "0.5.64",   "description": "Hydrogen's PLATFORM-GENERIC workspace layer on top of adom/core. Installs adom/core for the full Adom ecosystem, then adds everything common to running inside Hydrogen on ANY platform: the runtime-neutral hydrogen-* skills and the generic editor configuration (Claude Code CLI + extension, VS Code settings, trusted domains). Platform-specific layers depend on THIS: adom/hydrogen-windows-bootstrap (WSL2), adom/hydrogen-mac-bootstrap, adom/hydrogen-ubuntu-bootstrap. The reference design other orgs copy to build their own bootstrap on adom/core.",   "org": "adom",   "tags": [
skills/hydrogen-ai-agents/SKILL.md+4
@@ -86,6 +86,10 @@ few seconds; the human has minutes, not seconds, to click through Google or Open   CLI-side sign-in the VS Code panel keeps its Welcome screen until the window reloads; the   dialog offers "Reload VS Code now", or call `POST $HD/reload-vscode?confirm=1` (it hard   reloads the editor; ask first if the user may have unsaved editor state).+- **Kimi 403 "subscription does not have access to Kimi Code" from the CLI while the extension+  works**: that is the legacy pip Kimi 1.x (`kimi --version` says 1.x). Its upgrade also kills+  the TUI. Hydrogen's install (or hydrogen-bootstrap on its next run) replaces it with the 2.x+  binary in `~/.kimi-code/bin`, which uses the same credentials without error. - **Kimi region**: Kimi's installer defaults to mainland China (kimi.com, WeChat). Hydrogen's   install writes `global` into `~/.kimi-code/region` so sign-in goes to kimi.ai. If a user   lands on a WeChat page, that file is wrong.