{"version":"2.1.309","anchor":"print-mode-session-resume-now-runs-an-extra-async-step","canonical_anchor":"print-mode-session-resume-now-runs-an-extra-async-step","heading":"Resuming a session in print mode now does an extra step","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/print-mode-session-resume-now-runs-an-extra-async-step","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Resuming a session in print mode now does an extra step\n\nResuming a session in print mode now runs an extra step at the same time as the conversation history is loaded\n\n**Unclear.** What the extra step restores or does is not stated.\n\n**What**\n\nPrint mode is the way of running Claude Code with `-p`, where it answers once and exits instead of opening an interactive screen. When you resume an earlier session in print mode, Claude Code now runs an extra step at the same time as it loads the conversation history. If that step fails, the error is handled without stopping the resume.\n\n**Why**\n\nIt looks like more of the previous session is being restored after a resume.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}