session-timeout-handler

Claude Code workflows have a 2-minute timeout limit on tool execution. Handle timeouts by breaking tasks into chunks that complete within the limit, adding checkpoints after each chunk to save progress, and implementing resume logic to restart from the last checkpoint on interruption.

Chunking strategies break large batch operations into smaller groups that fit within time limits. Process items in batches, persist progress after each batch completes, and resume from the last completed batch if a timeout occurs, ensuring reliable completion of bulk operations.

Checkpoints persist workflow state after each completed chunk. On timeout or interruption, resume reads the last checkpoint and restarts from that point rather than from the beginning, eliminating duplicate work and ensuring long-running operations complete reliably.

Yes. Commands exceeding 60 seconds risk timeout within the 2-minute window. Break them into smaller operations with progress tracking between steps, checkpoint results after each step, and resume if interrupted to handle long-running commands safely.

Batch processing of multiple items, long-running commands over 60 seconds, bulk downloads, large API calls, and data-intensive tasks all risk timeout. Chunking and checkpoint patterns make these workloads reliable by breaking them into time-bounded segments with resumability.

Progress tracking logs completed chunks and current state. Resumability stores checkpoint data indicating where to restart. Together they provide visibility into workflow execution and enable safe re-runs from the last successful point without losing prior results.