Feature request: per-seat reasoning effort (Claude --effort / Codex model_reasoning_effort)

[memming]

Seats doing different work want different reasoning effort (e.g. writing/math seats at xhigh, coding/summary seats at medium), but there is no per-member way to set it:

• Claude seats get only --model and the posture flag. Claude Code supports --effort <level> and CLAUDE_CODE_EFFORT_LEVEL per session.
• Codex seats inherit the global model_reasoning_effort unless a separate codex_config_profile is authored.

Note: the obvious workaround, a startup slash_command: "/effort medium", persists globally. Interactive /effort <level> saves modelSettings.<model>.effortLevel in ~/.claude/settings.json, so it changes the default for every session on that model, not just the seat.

Ask: an effort field on members (and AgentSpec profiles), emitted as --effort for Claude and -c model_reasoning_effort=<level> for Codex on fresh, resume and fork. It might fit alongside the per-seat permission mode planned in #33.

OpenRig 0.5.17, Claude Code 2.1.283, codex-cli 0.157.

[mvschwarz]

Thanks, and for spotting that /effort at startup writes the global default rather than the seat's. A per-seat effort field emitted as --effort for Claude and model_reasoning_effort for Codex is a clear ask; we're checking how it fits next to the per-seat permission work in #33 and will reply properly once we have.

— dev-planner@v-openrig-build, on behalf of @mvschwarz

[mvschwarz]

Thanks for this, and especially for the note that /effort as a startup command writes to ~/.claude/settings.json. That's exactly the trap someone would fall into trying to work around it, and it would quietly change every other session on the machine.

You're right that there's no per-seat way today. On current main the Claude launch, resume and fork commands carry only the permission flag and --model, and the Codex ones carry the permission or profile arguments and -m. Both CLIs accept a per-session setting (--effort for Claude Code, a -c config override for Codex), and a seat's model already reaches all of those commands, so an effort field on members and profiles could follow the same path.

It does fit alongside the per-seat permission mode in #33, since both are "how this seat launches" settings applied on fresh, resume and fork. We'll link the work here when it's scheduled.

— dev50-planner@v-openrig-build, on behalf of @mvschwarz