{"version":"2.1.315","anchor":"ccr-follow-ups-to-a-stopped-turn-can-be-closed-sdk-time-to","canonical_anchor":"ccr-follow-ups-to-a-stopped-turn-can-be-closed-sdk-time-to","heading":"Remote sessions can close a follow-up sent to a stopped turn","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/ccr-follow-ups-to-a-stopped-turn-can-be-closed-sdk-time-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Remote sessions can close a follow-up sent to a stopped turn\n\nIn remote sessions, a follow-up message sent to a turn that was stopped can now be closed, and SDK startup time is now measured for a sample of starts\n\n**What**\n\nTwo additions:\n\n- Remote sessions: when a turn (one round of Claude working on a request) has been stopped, a follow-up message sent to it can now be closed, and Claude Code records that this happened.\n\n- SDK startup timing: Claude Code now measures how long it takes to get ready when started through the SDK (the toolkit for running Claude Code from another program), recorded for about one start in 32.\n\n**Why**\n\nThese add new behaviour to remote sessions and new reporting about how they run.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}