Skip to content

Reasoning-effort default: is high a product requirement #1718

Description

@chuks-qua

Parent

#1710

Question

Mcode defaults Codex turns to reasoning effort: high (packages/contracts/src/models/settings.ts). High effort delays first token substantially and may be the single largest component of the ~30s TTFT. Is high a deliberate product requirement, or should the default drop / become a prominent per-turn control?

The benchmark ticket quantifies how much of the 30s effort accounts for; this decision may be a cheap standalone win independent of any transport change.

Grill on: acceptable default per interaction mode (Plan vs Build), whether the user picks per turn already, and whether fast presets should imply lower effort.

Answer

Recorded on resolution: the new default(s) and where the control surfaces.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions