Skip to content

Add an /effort command to quickly switch reasoning effort for the current model #3074

@DrEsteban

Description

@DrEsteban

Describe the feature or problem you'd like to solve

Using the /model command to switch reasoning effort is multi-step and cumbersome.

I often want to adjust the reasoning effort of a prompt based on the complexity of the ask. For performance, I'll lower the reasoning effort to "Low" or "Medium" for straightforward requests. Then raise to "High" or "xHigh" when implementing features, design docs, multi-step workflows etc. I generally don't want to switch the actual model; I just want to adjust the reasoning effort.

The current experience for doing that using the /model command is fairly cumbersome. It's a multi-step process because the current model isn't highlighted by default; I must first navigate to the same model again, select it, then change the effort.

Proposed solution

Introduce an /effort command that allows you to switch reasoning effort on the same model in one command.

E.g.

  • /effort Medium or /effort med
  • /effort + arrow keys to select, Enter

Example prompts or workflows

Desired:

  1. Using Opus 4.7 on xHigh, I plan and implement a new feature. Great!
  2. "Hmmm, I want this variable to have a different name"
  3. /effort med
  4. "Rename this variable to X"
  5. /effort xhigh

Actual:

  1. Using Opus 4.7 on xHigh, I plan and implement a new feature. Great!
  2. "Hmmm, I want this variable to have a different name"
  3. /model
  4. Type "4.7"
  5. Use arrow keys to select Opus 4.7 again, Enter
  6. Use left/right arrow keys to select Medium, Enter
  7. "Rename this variable to X"
  8. /model
  9. Type "4.7"
  10. Use arrow keys to select Opus 4.7 again, Enter
  11. Use left/right arrow keys to select xHigh, Enter

Because it's so cumbersome today, I will often just execute the rename on xHigh which in my experience takes noticeably longer.

Additional context

I suppose another way to mitigate this would be: Have the currently selected model highlighted by default when you execute /model. That would allow me to just hit Enter and select the effort, eliminating much of the churn. However, I believe an /effort command to be the ideal solution here.

(FWIW: Claude Code CLI has this command 🙂)

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:modelsModel selection, availability, switching, rate limits, and model-specific behavior
    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions