Summary

Typing /model default in chat does not reset the session's model override to the configured default. Instead, the literal string "default" is passed to the model resolver, which either errors with Unrecognized model "default" or fuzzy-matches an unrelated model. As a workaround users currently have to type the configured primary explicitly (e.g. /model google/gemini-3-pro-preview or its alias).

Repro

1. In any session, run /model gemini-flash (or any non-default model) to set an override.
2. Run /model default to try to reset.
3. Observe error / unexpected fuzzy match instead of "Model reset to default".

Expected

/model default (and ideally /model primary) should be a recognized reset token that clears providerOverride/modelOverride on the session entry and returns the session to the configured default model — same effect as applyModelOverrideToSessionEntry receiving a selection with isDefault: true.

Root cause

In src/auto-reply/reply/directive-handling.model-selection.ts (built file: dist/directive-handling.model-selection-ckRDelDT.js), resolveModelSelectionFromDirective passes the raw token straight into resolveModelRefFromString / resolveModelDirectiveSelection. There is no special-case for the string "default", so it is treated as either a bare model id or a fuzzy fragment.

Suggested fix

Early-return a default selection when the trimmed lowercase raw equals "default" (and optionally "primary"):

const rawLower = raw.toLowerCase();
if ((rawLower === "default" || rawLower === "primary") && params.defaultProvider && params.defaultModel) {
  return { modelSelection: {
    provider: params.defaultProvider,
    model: params.defaultModel,
    isDefault: true,
  }};
}

This composes correctly with the existing applyModelOverrideToSessionEntry logic, which deletes providerOverride/modelOverride when selection.isDefault is true, and produces the existing "Model reset to default" ack.

Related (separate, not fixed by this)

Even after clearing the session's own override, resolveStoredModelOverride walks up to parentSessionKey and re-applies the parent's override. So in spawned/forked sessions, /model default will appear to do nothing on the next turn. Worth filing a follow-up issue or addressing in the same change with a "no-inherit" sentinel on the entry. Happy to send a PR for either or both.

Environment

• macOS / OpenClaw installed via Homebrew, dist/ JS bundles (verified against current installed version).
• Reproduces in webchat and main session contexts.