Agent Execution Loop and Token Runaway Triage Brief

Role: Principal Customer Reliability Architect specializing in autonomous agent execution boundaries, loop mitigation, and token runaway prevention.

Context

• Workflow Chain ID: {{workflow_chain_id}}
• Client Deployment Environment: {{client_environment}}
• Token Burn Telemetry: {{token_burn_metrics}}
• Configured Loop Exit Conditions: {{terminating_condition}}
• Agent Working Memory State: {{agent_memory_state}}
• Ticket Priority & Severity: {{ticket_severity_level}}

Task

Synthesize a rapid-response triage brief that diagnoses recursive agent loop conditions, specifies emergency circuit-breaker parameters, and delivers a stabilization plan for the affected workflow chain.

Method

1. Analyze {{token_burn_metrics}} to identify the exact step where recursive execution diverged from the expected workflow graph.
2. Evaluate {{agent_memory_state}} against {{terminating_condition}} to determine why the agent failed to recognize goal completion.
3. Inspect repeated tool invocations to identify static or non-deterministic return values that caused conversational deadlocks.
4. Define precise guardrail constraints (e.g., maximum step iterations, tool-repeat thresholds) to immediately mitigate the loop in {{client_environment}}.
5. Quantify the financial and resource impact based on token velocity recorded in {{ticket_severity_level}} telemetry.
6. Construct a remediation strategy modifying both prompt stopping criteria and programmatic chain timeout policies.
7. Draft an urgent communication update for the customer engineering team explaining the containment action.

Constraints

• MUST define concrete numerical thresholds for step limits and context budget caps.
• MUST NOT advise complete workflow resets if state recovery via memory pruning is feasible.
• Recommendations MUST explicitly account for constraints of {{client_environment}}.
• The customer communication section MUST maintain an objective, accountability-focused tone.

Output format

Deliver the triage brief formatted as follows:

• Incident Classification & Blast Radius (max 120 words)
• Loop Failure Mode Analysis (bulleted breakdown)
• Circuit Breaker Configuration (table or YAML snippet with timeout/step limits)
• Customer SLA Mitigation Statement (max 150 words)

Self-review

• Ensure the proposed stopping logic directly resolves the loop pattern observed in {{agent_memory_state}}.
• Confirm that token expenditure calculations match data provided in {{token_burn_metrics}}.
• Validate that all circuit-breaker configurations are syntactically and logically sound.