Skip to content

chore(devcontainer): start Claude Code at auto effort - #60

Open
justinmerrell wants to merge 2 commits into
mainfrom
chore/claude-auto-effort
Open

justinmerrell wants to merge 2 commits into
mainfrom
chore/claude-auto-effort

Conversation

@justinmerrell

@justinmerrell justinmerrell commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

What changes

The dev container no longer sets CLAUDE_CODE_EFFORT_LEVEL=max. The variable outranks /effort for the whole session, so /effort auto could not take effect:

Cleared effort from settings, but CLAUDE_CODE_EFFORT_LEVEL=max still controls this session

Without it, a session runs at the level /effort sets, or else the model's default (resolution order), and /effort auto clears a saved level. The README's feature list drops "starting at max effort", and docs/configuration.md drops the variable's index row; its Effort section now says why containerEnv leaves the variable unset.

It takes effect at the next container rebuild, because containerEnv is fixed when the container is created. The same change goes to each musher-dev repository whose dev container sets the variable.

Verification

Both versions of .devcontainer/devcontainer.json parse, and the only difference is the removed key. CI runs the gates.

🤖 Generated with Claude Code

The dev container set CLAUDE_CODE_EFFORT_LEVEL=max. The variable outranks
/effort for the whole session, so `/effort auto` only cleared the settings
file and the session stayed at max. Without it, Claude Code starts at the
model's default effort (auto), and /effort changes it again.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@justinmerrell
justinmerrell requested a review from a team as a code owner November 2, 2026 13:13
`auto` is not the default's name. Without CLAUDE_CODE_EFFORT_LEVEL, a session
runs at the level /effort sets, or else the model's default. /effort auto
clears a saved level, and the variable set to auto sends no level at all.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant