{"version":"2.1.300","anchor":"agent-summary-timer-now-uses-a-configured-wait-schedule-and","canonical_anchor":"agent-summary-timer-now-uses-a-configured-wait-schedule-and","heading":"Background agent summaries follow a wait schedule instead of a fixed timer","tier":"notice","area":"Subagents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/agent-summary-timer-now-uses-a-configured-wait-schedule-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Background agent summaries follow a wait schedule instead of a fixed timer\n\nProgress summaries for helper agents now follow a server-provided schedule of waits instead of a fixed interval, and skip until due\n\n**What**\n\nA subagent is a helper copy of Claude that works on part of a task in the background. Claude Code periodically writes a short summary of what each subagent is doing. These summaries used to run on a fixed interval.\n\nThe time between summaries now comes from a list of waits that Anthropic's servers provide, and the wait used depends on how many summaries have been made so far. If the next summary is not due yet, it is skipped.\n\nWhen summaries stop, Claude Code now sends a usage record with the number of summary calls, how many failed, how many summary lines were accepted, and which model families were used.\n\n**Why**\n\nEach summary is an extra call to the model. Spacing them out on a schedule changes how often those extra calls happen during long subagent work.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}