Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix feat: support effort level in agent definition frontmatter

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Add effort as a supported frontmatter field in .claude/agents/*.md agent definition files, similar to the existing model field.

Error Message

Note: xhigh and max are Opus-only — if effort is set to one of these on a non-Opus model, Claude Code should either warn or fall back gracefully.

Root Cause

Add effort as a supported frontmatter field in .claude/agents/*.md agent definition files, similar to the existing model field.

Fix Action

Fix / Workaround

Current workaround

Code Example

---
name: development-agent
description: Implements GitHub issues end-to-end
model: opus
effort: xhigh
---
RAW_BUFFERClick to expand / collapse

Summary

Add effort as a supported frontmatter field in .claude/agents/*.md agent definition files, similar to the existing model field.

Motivation

Currently the only way to control effort level is globally via settings.json → effortLevel. But different agents have very different complexity profiles — a deal-hunting agent doing web scraping needs low effort, while a development agent implementing GitHub issues needs xhigh. There's no way to express this per-agent today.

Proposed API

---
name: development-agent
description: Implements GitHub issues end-to-end
model: opus
effort: xhigh
---

Accepted values should match the API: low, medium, high, xhigh, max.

Note: xhigh and max are Opus-only — if effort is set to one of these on a non-Opus model, Claude Code should either warn or fall back gracefully.

Current workaround

Only global effortLevel in settings.json is available. Per-agent effort is not configurable.

Related issues

#64706, #43083, #63599, #65531, #64033

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING