{"version":"2.1.318","anchor":"print-resume-now-registers-session-metadata-and-clears-it","canonical_anchor":"print-resume-now-registers-session-metadata-and-clears-it","heading":"Resuming a session in --print mode now keeps a record of that session","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/print-resume-now-registers-session-metadata-and-clears-it","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Resuming a session in --print mode now keeps a record of that session\n\nWhen you resume a session with --print, Claude Code stores a record of where it came from and deletes that record if the resume fails\n\n**Unclear.** What, if anything, this changes that you can see when resuming with --print is not clear.\n\n**What**\n\n`--print` runs Claude Code without its interactive screen. When you resume a session this way, Claude Code now stores a record of it, including:\n\n- Where it came from: a file, a web address, a store or a remote session\n\n- Whether it runs through an SDK worker\n\n- That it is running without a screen\n\nIf the resume fails, the record is deleted. In some cases the final cleanup step is skipped.\n\n**Why**\n\nThis lets Claude Code keep track of sessions resumed in print mode.\n\n- Area: Sessions\n- Names: `--print`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}