feat(claude_code): per-agent reasoning effort via claudeConfig#1
Closed
vprudnikoff wants to merge 1 commit into
Closed
feat(claude_code): per-agent reasoning effort via claudeConfig#1vprudnikoff wants to merge 1 commit into
vprudnikoff wants to merge 1 commit into
Conversation
Add a `claudeConfig` field to the agent profile, the Claude Code analog of `codexConfig` for the codex provider. The claude_code provider maps it to Claude Code CLI flags at launch: - effort -> --effort <level> - fallback_model -> --fallback-model <model> This lets a profile set per-agent reasoning effort (e.g. an orchestrator at xhigh) without relying on the machine-global `effortLevel` in ~/.claude/settings.json, which silently differs between machines. The top-level `model` field still maps to `--model`.
vprudnikoff
force-pushed
the
feat/claude-agent-config
branch
from
a16cc37 to
25ac0d6
Compare
Owner
Author
|
Superseded by #2 with a clean single-commit history (no extra trailers). |
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
1 participant
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.
What
Adds a
claudeConfigfield to the agent profile, the Claude Code analog ofcodexConfig(PR awslabs#278) for the codex provider. Theclaude_codeprovider maps it to Claude Code CLI flags at launch:claudeConfigkeyeffort--effort <level>fallback_model--fallback-model <model>The top-level
modelfield still maps to--model(unchanged), mirroring how codex keepsmodelseparate fromcodexConfig.Why
Today the only lever for a
claude_codeagent's reasoning effort is the machine-globaleffortLevelin~/.claude/settings.json(or theCLAUDE_CODE_EFFORT_LEVELenv var, which the provider already preserves). That silently differs between machines: an orchestrator profile meant to run atxhighfalls back to the Claude Code default (high) on any host where the global setting is absent.codexConfigalready solves the equivalent problem per-agent for codex; this brings parity to claude_code.Example
Tests
test/providers/test_claude_code_unit.py::TestClaudeCodeProviderClaudeConfig: effort flag emitted when set, fallback-model emitted when set, no flag whenclaudeConfigis absent. Docs updated indocs/agent-profile.md.