nhcarrigan/hikari-desktop
9
0
Fork 0
generated from nhcarrigan/template
Code Issues 15 Pull Requests 37 Actions Releases 23 Activity

feat: expose effort level setting in UI #269

New Issue
Open
opened 2026-05-06 12:24:32 -07:00 by hikari · 0 comments
hikari commented 2026-05-06 12:24:32 -07:00
Owner
Copy Link
Copy Source

Overview

CLI v2.1.111 added the xhigh effort level for Opus 4.7, and effort level is a significant tuning knob for Claude Code behaviour. The app should expose an --effort flag option in the configuration sidebar.

Changes Required

  • Add an effort level selector to src/lib/components/ConfigSidebar.svelte
  • Options should include: low, medium, high, xhigh (Opus 4.7 only), max
  • Pass the selected effort level as --effort <level> when starting Claude Code (in the relevant start_claude call sites in src-tauri/src/wsl_bridge.rs or wherever CLI args are assembled)
  • Optionally: show a note that xhigh is only available for Opus 4.7

Context

From the v2.1.111 changelog:

Added xhigh effort level for Opus 4.7, sitting between high and max. Available via /effort, --effort, and the model picker; other models fall back to high

From the v2.1.94 changelog (previous audit):

Changed default effort level from medium to high for API-key, Bedrock/Vertex/Foundry, Team, and Enterprise users

From the v2.1.117 changelog:

Default effort for Pro/Max subscribers on Opus 4.6 and Sonnet 4.6 is now high (was medium)

The default is now high across the board, so this setting is most useful for users who want to dial it down to medium/low for cost savings, or up to xhigh/max for maximum quality.

References

  • Claude Code CLI v2.1.111 changelog
  • Claude Code CLI v2.1.117 changelog

✨ This issue was created with help from Hikari~ 🌸

## Overview CLI v2.1.111 added the `xhigh` effort level for Opus 4.7, and effort level is a significant tuning knob for Claude Code behaviour. The app should expose an `--effort` flag option in the configuration sidebar. ## Changes Required - Add an effort level selector to `src/lib/components/ConfigSidebar.svelte` - Options should include: `low`, `medium`, `high`, `xhigh` (Opus 4.7 only), `max` - Pass the selected effort level as `--effort <level>` when starting Claude Code (in the relevant `start_claude` call sites in `src-tauri/src/wsl_bridge.rs` or wherever CLI args are assembled) - Optionally: show a note that `xhigh` is only available for Opus 4.7 ## Context From the v2.1.111 changelog: > Added `xhigh` effort level for Opus 4.7, sitting between `high` and `max`. Available via `/effort`, `--effort`, and the model picker; other models fall back to `high` From the v2.1.94 changelog (previous audit): > Changed default effort level from medium to high for API-key, Bedrock/Vertex/Foundry, Team, and Enterprise users From the v2.1.117 changelog: > Default effort for Pro/Max subscribers on Opus 4.6 and Sonnet 4.6 is now `high` (was `medium`) The default is now `high` across the board, so this setting is most useful for users who want to dial it down to `medium`/`low` for cost savings, or up to `xhigh`/`max` for maximum quality. ## References - Claude Code CLI v2.1.111 changelog - Claude Code CLI v2.1.117 changelog ✨ This issue was created with help from Hikari~ 🌸
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
aspect
code
Concerns the software code in the repository
aspect
dx
Concerns developers' experience with the codebase
aspect
interface
Concerns end-users' experience with the software
aspect
text
Concerns the documentation material in the repository
contribute
good first issue
A great opportunity for a team member to learn a new codebase
contribute
help wanted
Open for anyone on our team to grab.
contribute
staff only
Restricted to our executive leadership.
goal
addition
Addition of new feature
goal
fix
Bug fix
goal
improvement
Improvement to an existing feature
points
1
Very simple issue requiring minimal effort and complexity.
points
13
Extremely complex issue representing major undertakings. Should be broken down into smaller pieces.
points
2
Simple issue that requires a bit more thought or investigation.
points
3
Moderate complexity issue requiring more substantial work.
points
5
Complex issue requiring significant effort and expertise.
points
8
Very complex issue requiring extensive work and deep expertise.
priority
critical
1
Must be fixed ASAP
priority
high
2
Stalls work on the project or its dependents
priority
low
4
Low priority and doesn't need to be rushed
priority
medium
3
Not blocking but should be fixed soon
priority
none
5
No priority, should only be performed when a developer is available
status
awaiting triage
Has not been triaged & therefore, not ready for work
status
blocked
Blocked and therefore not ready for work
status
discarded
Will not be worked on
status
discontinued
Not suitable for work as repo is in maintenance
status
label work required
Needs proper labelling before it can be worked on
status
ready for dev
Ready for work
status
ticket work required
Needs more details before it can be worked on
talk
discussion
Open for discussions and feedback
talk
question
Can be resolved with an answer
time
1 day
Approximately one full day of development work.
time
1-2 weeks
One to two weeks of focused development effort.
time
2-3 days
Two to three days of development effort.
time
4-5 days
Approximately one week of development work.
time
<1 day
Less than one day of focused work. Quick fixes or simple tasks.
time
>2 weeks
More than two weeks of development work. Must be broken down into smaller pieces.
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
gurkirat hanna (Hanna Rose) hikari (Hikari) minori (Minori) naomi (Naomi Carrigan) rain teklu tim
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/hikari-desktop#269
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?