{"version":"2.1.301","anchor":"subagent-sends-hook-point-and-exit-flush-no-longer-waits-on","canonical_anchor":"subagent-sends-hook-point-and-exit-flush-no-longer-waits-on","heading":"Exiting no longer waits for a sign-in token refresh","tier":"notice","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/subagent-sends-hook-point-and-exit-flush-no-longer-waits-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Exiting no longer waits for a sign-in token refresh\n\nOn one exit path, Claude Code now sends its final usage data without waiting for a sign-in token refresh that is in progress\n\n**What**\n\nWhen Claude Code closes on one of its exit paths, it sends any remaining usage data first. It now does this without waiting for a sign-in token refresh (the renewal of the credential that keeps you logged in) that may be in progress.\n\nSeparately, agents gain an internal connection point for messages sent by subagents, helper runs of Claude that do part of a task. It can be set up only once per agent; a second attempt is refused with an error.\n\n**Why**\n\nClaude Code should no longer hang on exit while a sign-in token is being renewed.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}