Motivation
The agent has no maxTurns limit. An unbounded session could:
- Run indefinitely without natural checkpoints
- Accumulate a very large context window that degrades response quality
- Consume significant tokens on a single session without the user noticing
The Claude Code subagent spec supports a maxTurns frontmatter field.
Proposed Change
Add a maxTurns value to coach.md frontmatter. A coaching session should be time-boxed — a reasonable limit might be:
40 turns allows a substantive session (roughly 20 human + 20 agent turns) while creating a natural checkpoint. When the limit is reached the agent should (if possible) trigger session wrap-up behaviour (see #8).
Considerations
- The right value depends on typical session length; 40 is a starting point for discussion
- This could also help prevent accidental runaway sessions if the user leaves a session open
- Should be documented in README as a session length guideline
Motivation
The agent has no
maxTurnslimit. An unbounded session could:The Claude Code subagent spec supports a
maxTurnsfrontmatter field.Proposed Change
Add a
maxTurnsvalue tocoach.mdfrontmatter. A coaching session should be time-boxed — a reasonable limit might be:40 turns allows a substantive session (roughly 20 human + 20 agent turns) while creating a natural checkpoint. When the limit is reached the agent should (if possible) trigger session wrap-up behaviour (see #8).
Considerations