Timeouts & Limits
Testy Claw has two primary safety limits: maxSteps caps the number of tool calls per run, and timeout caps how long each individual tool call can take.
maxSteps
The agent stops after this many tool calls, even if the task is not complete. The run exits with code 2 and prints a partial summary.
| Scenario | Recommended maxSteps |
|---|---|
| Simple file edits | 5–10 |
| Scaffolding a new feature | 15–25 |
| Large refactors | 30–50 |
| CI pipeline tasks | 10 (conservative) |
timeout
Each tool call is killed after timeout milliseconds. The error is fed back to the model, which can retry or skip the step. The run exits with code 3 if a timeout causes the task to fail.
claw.config.ts
export default defineConfig({
maxSteps: 20,
timeout: 30_000, // 30 seconds per tool call
// Override per-run via CLI:
// testy-claw run "task" --max-steps 5
// CLAW_TIMEOUT=60000 testy-claw run "task"
});maxRetries
When a tool call fails (throws or times out), the agent retries up to maxRetries times before giving up on that step.
TipSet
maxRetries: 0 in CI to fail fast rather than retrying on transient errors.