{"version":"2.1.280","anchor":"sidequery-api-dispatch-gains-an-effort-output-configef","canonical_anchor":"new-max-effort-mode-with-effort-command","heading":"New 'max effort' mode with a status-line reminder","tier":"use","area":"API Dispatch","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/sidequery-api-dispatch-gains-an-effort-output-configef","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New 'max effort' mode with a status-line reminder\n\nA new max-effort mode sends an effort parameter to the API and shows a status-line reminder (with \/effort to change it) when active\n\n**What**\n\n- A new \"max effort\" mode was added: a helper decides when to force maximum effort, gated by a reminder-enabled check before it's applied.\n\n- A status-line reminder (\"Max effort \u00b7 \u2026 \u00b7 \/effort to change\") is shown when effort is set to max; whether it appears is controlled by the `CLAUDE_CODE_MAX_EFFORT_REMINDER` environment variable, falling back to a remote flag (`tengu_proud_clover`, off by default unless enabled server-side).\n\n- The VS Code extension's feature-gate table gained the corresponding max-effort reminder gate, wired from `maxEffortReminderEnabled`.\n\n- The reminder is shown in a warning color rather than a subtle one when the environment variable or flag is set.\n\n- Underneath, the request-building code for side-queries now accepts an `effort` option that becomes `output_config.effort` on the API call; if a model rejects it, Claude Code remembers the model doesn't support it and retries without the field, logging a telemetry event.\n\n**Why**\n\nThis lets you run Claude Code at maximum effort and know at a glance when that mode is active, via `\/effort` to change it, while the underlying request logic gracefully falls back for models that don't support the effort parameter.\n\n- Area: API Dispatch\n- Names: `output_config.effort`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 4\/5"}