Skip to content

docs(global-settings): finish the toast correction, harden the CLI-path snippet #718

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
WilcoLouwerse merged 2 commits into from
Sep 10, 2026
Merged

docs(global-settings): finish the toast correction, harden the CLI-path snippet #718

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
21399ec
docs(global-settings): finish the toast correction, harden the CLI-pa…
WilcoLouwerse Sep 8, 2026
87bee33
docs(global-settings): sort by mtime, not lexicographically, for the …
WilcoLouwerse Sep 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions docs/claude/global-claude-settings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -464,8 +464,11 @@ Restart the session and verify which model is actually served:

```bash
# The VSCode extension ships its own CLI and does not put `claude` on your PATH.
# If `command -v claude` comes up empty, point at the bundled binary instead:
CLAUDE="$(command -v claude || echo ~/.vscode-server/extensions/anthropic.claude-code-*/resources/native-binary/claude)"
# If `command -v claude` comes up empty, point at the bundled binary instead.
# VSCode keeps several extension versions during an upgrade, so take the newest
# match by modification time rather than letting the glob expand to more than
# one path — a plain lexicographic sort would pick e.g. 1.9.0 over 1.10.0.
CLAUDE="$(command -v claude || ls -1dt ~/.vscode-server/extensions/anthropic.claude-code-*/resources/native-binary/claude 2>/dev/null | head -1)"
"$CLAUDE" -p "Reply with exactly the word ok" --output-format json | jq '.modelUsage | keys'
```

Expand All @@ -479,7 +482,7 @@ The result should list the model you pinned (e.g. `["claude-opus-5"]`). Swapping
/model fable
```

The CLI confirms with "Set model to Fable 5.1 for this session only" and the switch is live. The `Failed to set model: EPERM` toast that follows is the extension's failed attempt to *persist* the choice — ignore it; nothing was lost, and the next session starts on your pinned default again. That is the intended behaviour under this setup: the default stays the cheaper model, using a heavier one is a deliberate, visible act each time.
The CLI confirms with "Set model to Fable 5.1 for this session only" and the switch is live. The "for this session only" wording is Claude Code telling you the persist was refused — nothing was lost, and the next session starts on your pinned default again. Reach for the picker instead and you get the `Failed to set model: EPERM` toast with no switch at all. That split is the intended behaviour under this setup: the default stays the cheaper model, and using a heavier one is a deliberate, visible act each time.

**Fix — one-off switch.** If you only need to change the persisted model once, run the unlock step from [README → Updating](../../global-settings/README.md#updating) in your own terminal, switch the model in Claude Code, then run the relock step. Don't skip the relock.

Expand Down
Loading