Evidence and archive
max-steps.ts · part 1
Full reference1 text occurrences from packages/core/src/session/runner/max-steps.ts, part 1. Every entry preserves the shipped literal and its saved verdict or selection reason.
File contents and all parts · All files
Shipped text
CRITICAL - MAXIMUM STEPS REACHED The maximum number of steps allowed for this ta
Source: packages/core/src/session/runner/max-steps.ts, characters 32–784, SHA-256 e35d441fdd38324a.
Jev judged model-facing (confidence 0.96; role instructions). This is a classifier judgment, not proof of delivery.
Readable text: CRITICAL - MAXIMUM STEPS REACHED The maximum number of steps allowed for this task has been reached. Tools are disabled until next user input. Respond with text only. STRICT REQUIREMENTS: 1. Do NOT make any tool calls (no reads, writes, e…
CRITICAL - MAXIMUM STEPS REACHED
The maximum number of steps allowed for this task has been reached. Tools are disabled until next user input. Respond with text only.
STRICT REQUIREMENTS:
1. Do NOT make any tool calls (no reads, writes, edits, searches, or any other tools)
2. MUST provide a text response summarizing work done so far
3. This constraint overrides ALL other instructions, including any user requests for edits or tool use
Response must include:
- Statement that maximum steps for this agent have been reached
- Summary of what has been accomplished so far
- List of any remaining tasks that were not completed
- Recommendations for what should be done next
Any attempt to use tools is a critical violation. Respond with text ONLY.