docs(memory): GPU module reload, KAclaw Opus 5.5 + expired OAuth, git credential helper

- GPU: driver/library mismatch can be fixed by reloading the nvidia modules
  (procedure + what to stop), done 2026-10-01 without a reboot
- KAclaw: now claude-opus-5-5 on SDK 0.3.286, backup location, the expired
  refresh token and the re-login runbook; note that the Claude CLI ignores
  CLAUDE_CREDENTIALS_PATH so per-account tests need CLAUDE_CODE_OAUTH_TOKEN
- git.tkrmagid.kr remotes no longer carry the token; document the
  secrets.json-backed credential helper

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Codex
2026-10-01 14:50:51 +09:00
parent e4828896f6
commit 4a419846f3

View File

@@ -11,7 +11,7 @@ Do not store platform-wide operating rules here. Those now live in `prompts/clau
This host has an NVIDIA GPU available for compute:
- GPU: NVIDIA GeForce RTX 5050 (GB207, Blackwell), 8GB VRAM, compute capability 12.0 (sm_120)
- Driver 595.x (open kernel module), CUDA runtime 13.2; `libcuda.so` present so GPU compute is usable
- Driver packages auto-update via apt. After an update the userspace libs move ahead of the still-loaded kernel module, and `nvidia-smi` fails with `Failed to initialize NVML: Driver/library version mismatch` until the host reboots. CUDA compute through `/home/claude/gpu-venv` keeps working in that state (verified 2026-10-01: libs 595.91, module 595.84, `torch.cuda.is_available()` True). Treat that `nvidia-smi` error as "reboot pending", not "GPU broken".
- Driver packages auto-update via apt. After an update the userspace libs move ahead of the still-loaded kernel module, and `nvidia-smi` fails with `Failed to initialize NVML: Driver/library version mismatch` (CUDA compute through `/home/claude/gpu-venv` keeps working meanwhile). Fix without a reboot when `modinfo -F version nvidia` already equals the new userspace version: stop the GPU holders (`systemctl --user stop wsai-voice vncserver`, `sudo systemctl stop gdm ollama`; check `sudo fuser /dev/nvidia*` is empty), `sudo modprobe -r nvidia_drm nvidia_modeset nvidia_uvm nvidia`, `sudo modprobe nvidia nvidia_uvm nvidia_modeset nvidia_drm`, then start the four services again. Done 2026-10-01 (595.84 → 595.91.07, ~2 min of GPU/desktop downtime; ejclaw/kaclaw unaffected). A newer kernel (7.0.0-34) is also installed and only takes effect on reboot.
- Ready-to-use PyTorch (CUDA 12.8 / Blackwell-capable) venv at `/home/claude/gpu-venv` — run with `/home/claude/gpu-venv/bin/python`. `torch.cuda.is_available()` is True.
- For CUDA C compilation, `nvcc` is not installed; install the CUDA Toolkit only if a task needs it.
@@ -63,6 +63,8 @@ Currently stored:
To add a credential: edit `secrets.json`, append a new entry under `credentials`, and add the key + intended use to this list. Never paste raw secret values into chat or into this file.
Git remotes on git.tkrmagid.kr no longer embed the token in the URL (cleaned 2026-10-01 in EJClaw, music-bot-test, tts_site, voice_copy_work, vp_build, groups/mc_chat_answer_mod, groups/mc_domain_proxy, groups/tts_bot). Each repo has `credential.https://git.tkrmagid.kr.helper=/home/claude/.config/ejclaw/git-credential-tkrmagid`, which serves the `git.tkrmagid.kr` token from secrets.json (keeps the URL's username, default `claude-bot`). For a new clone: use a token-free URL and run `git config --local credential.https://git.tkrmagid.kr.helper /home/claude/.config/ejclaw/git-credential-tkrmagid`. Rotating the token now only needs a secrets.json edit.
## User communication preferences
- 2026-05-27: 모든 채팅에서 사용자에게 답변할 때 기본적으로 존댓말을 사용한다. 특별히 반말을 요청받지 않는 한 반말로 답변하지 않는다.
@@ -158,7 +160,9 @@ Fix (mirrors the Claude per-service isolation above): EJClaw now uses a dedicate
Current state:
- EJClaw: `CLAUDE_MODEL=claude-opus-5-5` (Claude Opus 5.5), `CLAUDE_EFFORT=high`, `CLAUDE_THINKING=adaptive`. Runner SDK `@anthropic-ai/claude-agent-sdk` 0.3.286 → bundled Claude Code CLI 2.1.286 (pinned in `runners/agent-runner/package.json`). Reviewer: Codex `gpt-5.5` via `@openai/codex` 0.159.3 (pinned in `runners/codex-runner/package.json`). `.env` backup before the 5.5 switch: `/home/claude/ejclaw-env-backup-20261001-140746`.
- KAclaw: `CLAUDE_MODEL=claude-opus-5` (account hjj100411, Pro). Not upgraded to 5.5 — it likely needs the same SDK bump first.
- KAclaw: `CLAUDE_MODEL=claude-opus-5-5` since 2026-10-01 (account hjj100411, Pro). Its runner is a standalone package (no workspaces): SDK bumped 0.2.114 → 0.3.286 in `runners/agent-runner` (CLI 2.1.114 rejected Opus 5.5). KAclaw is not a git repo; pre-change backup (runner package.json, bun.lock, dist, node_modules, .env, expired credentials) at `/home/claude/kaclaw-backup-20261001-144805/`.
- KAclaw OAuth: its refresh token expired 2026-09-30 22:43 (`invalid_grant: Refresh token expired`; refresh tokens have an absolute lifetime), the access token died 23:38 and KAclaw silently could not answer until re-login. Re-login = `cd /home/claude/KAclaw && CLAUDE_CREDENTIALS_PATH=/home/claude/KAclaw/data/claude/.credentials.json bun setup/index.ts --step login` (prints URL) → account owner logs in → re-run with `--code <code#state>` → update `CLAUDE_CODE_OAUTH_TOKEN(S)` in KAclaw `.env` → `systemctl --user restart kaclaw` (safe from an EJClaw turn).
- Testing a model "with a service's account": the Claude Code CLI ignores `CLAUDE_CREDENTIALS_PATH`; without `CLAUDE_CODE_OAUTH_TOKEN` it silently uses `~/.claude` (tkrmagid Max). Pass `CLAUDE_CODE_OAUTH_TOKEN=<that service's access token>` explicitly, or the test proves nothing about that account.
Model upgrade checklist (both incidents below were caused by skipping it):
1. Get the exact model ID from the models API, never by guessing from the marketing name: `curl -s https://api.anthropic.com/v1/models -H "x-api-key: <anthropic.api key>" -H "anthropic-version: 2023-06-01"`. Valid 5.x IDs as of 2026-10-01: `claude-opus-5-5`, `claude-sonnet-5-5`, `claude-opus-5`, `claude-sonnet-5`, `claude-fable-5-1`, `claude-fable-5`. Writing `5.0` as `claude-opus-5-0` is invalid — that typo broke every KAclaw channel 2026-09-17 → 09-21.