From 49552b3485ef67ab63b71e74ba25074ac606dc83 Mon Sep 17 00:00:00 2001 From: Tom Boucher Date: Mon, 6 Jul 2026 22:57:39 -0400 Subject: [PATCH] docs(#2003): add changeset fragment for --runtime override --- .changeset/noble-foxes-purr.md | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 .changeset/noble-foxes-purr.md diff --git a/.changeset/noble-foxes-purr.md b/.changeset/noble-foxes-purr.md new file mode 100644 index 000000000..8f49e2e58 --- /dev/null +++ b/.changeset/noble-foxes-purr.md @@ -0,0 +1,5 @@ +--- +type: Fixed +pr: 0 +--- +**`capability state` and `loop render-hooks` now accept `--runtime` to override the auto-detected runtime** — previously both commands parsed only `--config-dir`, so the runtime config dir was derived from the persisted `.planning/config.json` runtime (precedence `GSD_RUNTIME` → `config.runtime` → `claude`). A repo that persisted `runtime:"codex"` resolved the config dir to `~/.codex`, where the Claude skill isn't installed, so every skill-bearing capability reported `surfaced:false` and `execute:post`/`verify:post` hooks silently no-op'd when the operator drove GSD from Claude Code. `--runtime ` (canonicalized, so aliases like `codex-app` work) now bypasses that fallback so the config dir resolves to the explicitly-named runtime's home. Behavior without the flag is unchanged. (#2003)