feat(config): Add configurable maxTurns with default of 50

[gricha]

Summary

• Add maxTurns config option to warden.toml at both defaults and per-trigger levels
• Increase default from 5 to 50 to prevent error_max_turns during thorough analysis
• Precedence: trigger.maxTurns > defaults.maxTurns > hardcoded default (50)

Example

version = 1

[defaults]
maxTurns = 30

[[triggers]]
name = "thorough-review"
event = "pull_request"
actions = ["opened"]
skill = "security-review"
maxTurns = 100  # override for this trigger

Test plan

• Added schema validation tests for maxTurns
• All existing tests pass

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
warden	Ready	Preview, Comment	Jan 30, 2026 6:23pm

[sentry-warden]

find-bugs

find-bugs: Found 1 issue (1 medium)

---

_{⏱ 69.5s · 175.6k in / 3.1k out · $0.38}

[sentry-warden]

🟠 10x increase in maxTurns default may cause resource exhaustion

The default maxTurns value was increased from 5 to 50. This 10x increase could lead to significantly longer execution times and higher API costs if the analysis gets stuck in a loop or takes many iterations. While 5 turns may have been too restrictive for complex analysis, 50 turns without any timeout or cost guard could be excessive.

Suggested fix: Consider a more moderate increase (e.g., 15-20) or add a cost/time guard to prevent runaway analysis. Also consider making this configurable per-skill if different skills have different complexity needs.

Suggested change

	const { maxTurns = 50, model, abortController, pathToClaudeCodeExecutable } = options;
	const { maxTurns = 15, model, abortController, pathToClaudeCodeExecutable } = options;

---

_{warden: find-bugs}