claude-code - 💡(How to fix) Fix Surface current Effort level as an icon in the input toolbar (VS Code) [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#54641Fetched 2026-04-30 06:40:04
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

In the Claude Code VS Code extension, the Effort setting (Low / Medium / High) is currently only visible after opening the command menu and scrolling to the Model section. It would be much more useful to surface the current Effort level as a small icon/indicator in the input toolbar, alongside the + (attach) and / (commands) icons.

Problem

  • I can't tell at a glance what Effort level I'm currently using.
  • To check or change it, I have to open the menu and navigate to Model → Effort, which adds friction during active sessions.
  • It's easy to forget the mode is set to Low when working on something that warrants High effort (or the reverse, wasting tokens on trivial tasks).

Proposed Solution

Add a small Effort indicator to the input toolbar (the row with +, /, and Auto mode). Ideas:

  • A compact label like L / M / H, or the dot-indicator style already used in the Effort menu.
  • Clicking it opens the Effort selector directly, skipping the full command menu.
  • Optional: subtle color cue (e.g., higher effort = warmer color) for fast visual recognition.

Why it matters

Effort directly affects response quality, latency, and token usage. Making it a first-class, always-visible control — the way model selection often is in other tools — would help users make intentional choices instead of discovering mid-task that they were on the wrong setting.

<img width="1536" height="960" alt="Image" src="https://github.com/user-attachments/assets/ce488070-6863-4d28-852e-acd88c683dd3" />

Alternative Solutions

No response

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

No response

Additional Context

No response

extent analysis

TL;DR

Add an Effort indicator to the input toolbar to provide a visible and easily accessible display of the current Effort level.

Guidance

  • Review the existing command menu and Model section to understand how the Effort setting is currently implemented and how it can be integrated into the input toolbar.
  • Consider using a compact label or dot-indicator style for the Effort indicator, and explore the option of adding a subtle color cue for fast visual recognition.
  • Determine the best approach for opening the Effort selector directly when the indicator is clicked, potentially by leveraging existing menu navigation logic.
  • Evaluate the potential impact on user experience and token usage of making the Effort setting a first-class, always-visible control.

Example

No code snippet is provided as the issue does not contain specific implementation details.

Notes

The proposed solution aims to reduce friction during active sessions and help users make intentional choices about their Effort level. However, the implementation details and potential technical challenges are not explicitly stated in the issue.

Recommendation

Apply workaround: Add an Effort indicator to the input toolbar, as it would provide a visible and easily accessible display of the current Effort level, addressing the user's pain points and improving the overall user experience.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Surface current Effort level as an icon in the input toolbar (VS Code) [1 participants]