{"version":"2.1.246","anchor":"rewinding-a-remote-session-now-stops-the-background-agents-i","canonical_anchor":"rewinding-a-remote-session-now-stops-the-background-agents-i","heading":"Rewinding a remote session now stops the background agents it rewound past","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/rewinding-a-remote-session-now-stops-the-background-agents-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Rewinding a remote session now stops the background agents it rewound past\n\nRewinding a remote session now stops the background agents started inside the rewound span.\n\n**What**\n\nBefore a rewind, Claude walks the task list to work out which local background agents were started inside the span being rewound, stops them, and emits their completed, failed or stopped status. Any permission prompt left parked is retired with a new reason of `rewind` rather than lingering.\n\n**Details**\n\n- Agents rooted at an in-process teammate are skipped rather than stopped.\n- Whether the running\/requires-action gating applies is decided by the existing environment variable `CLAUDE_CODE_BG_TASKS_REPORT_RUNNING`; unset keeps the older behaviour path. That variable is now read in several more places than before.\n\n**Evidence**\n\n`parkedPermissionReason: \"rewind\"`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}