openai / openai/codex-plugin-cc

Feature: support default model and effort settings in /codex:setup

Open
#44 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
33.3k
Forks
2.3k
PR merge metrics
No merged PRs in 30d

Description

Add support for persisting default --model and --effort values via /codex:setup, so users don't have to pass them on every command invocation.

Motivation

Currently, --model and --effort must be specified per-command. Users who consistently prefer a specific model (e.g., gpt-5.4) or effort level (e.g., xhigh) have to repeat these flags every time they run /codex:rescue, /codex:review, or /codex:adversarial-review.

The setup command already persists state like the review gate toggle, so it's a natural place for these defaults.

Proposed UX

/codex:setup --default-model gpt-5.4 --default-effort xhigh
  • Defaults would apply to all commands (task, review, adversarial-review) unless overridden per-invocation with explicit --model or --effort flags.
  • /codex:setup (without flags) and /codex:status would display the current defaults.

Additional context

  • --effort is currently only supported on task (rescue), not on review or adversarial-review. It may make sense to extend --effort support to review commands as part of this work.
  • Claude Code's /fast mode toggle could also be worth supporting.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how /codex:setup persists the review gate and how /codex:status reads it, then follow option handling for task, review, and adversarial-review. Done means setup can store and display model and effort defaults, commands use them unless explicitly overridden, and the supported scope for review effort is resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
cli, developer-experience
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.