feat: configurable default effort level via .beans.yml (Refs: beans-85nf)#148
Merged
Conversation
- Add `agent.default_effort` field to `AgentConfig` in `.beans.yml` (values: low, medium, high, max) - Add `Config.GetDefaultEffort()` method with validation - Add `Manager.SetDefaultEffort()` and `newBaseSession()` helper to apply defaults to all new sessions - Wire config into serve.go via `agentMgr.SetDefaultEffort(cfg.GetDefaultEffort())` - Fix AgentComposer.svelte to not hardcode `!effort` as visual fallback for "High" Refs: beans-85nf Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Refs: beans-85nf Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
GetDefaultEffort() now returns the raw configured value. IsValidEffortLevel() validates it. serve.go guards against invalid values; check.go reports them as config errors — matching the pattern used for default_type. Refs: beans-85nf Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Owner
|
Good catch, thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While updating beans locally I noticed higher token usage than expected. The effort feature added in beans-pw99 introduced
|| !effortinAgentComposer.svelte, which visually defaulted to "High" when no effort was set — and since new sessions had no effort set, every session effectively ran at high thinking effort. This restores the Claude CLI's own default unlessagent.default_effortis explicitly set in.beans.ymlor changed in the UI.Invalid
agent.default_effortvalues are caught bybeans checkrather than silently ignored, consistent with howdefault_typeis handled.Tested manually.