{"version":"2.1.317","anchor":"session-resume-skips-virtual-meta-messages-and-gains-session","canonical_anchor":"session-resume-skips-virtual-meta-messages-and-gains-session","heading":"Resuming a session continues from your last real message","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/session-resume-skips-virtual-meta-messages-and-gains-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Resuming a session continues from your last real message\n\nResume now picks up from a real message rather than a hidden one, sessions record an owner, and scheduled tasks follow file links and apply size limits\n\n**Unclear.** It is not stated what the new session owner value changes for a user.\n\n**What**\n\nWhen you resume a saved conversation, Claude Code has to choose which message to continue from. It used to take any message that was not part of a side conversation. It now prefers messages that are part of the real conversation. It skips behind-the-scenes messages that Claude Code adds itself and that you never wrote.\n\nOther changes in the same area:\n\n- Sessions now load a session owner value along with their other saved details.\n\n- `\/resume` now applies a limit when it loads extra details for the sessions in its list.\n\n- Scheduled tasks now follow symbolic links, which are files that point to another file, and apply size limits.\n\n**Why**\n\nThese changes make resuming more dependable. A resumed conversation should continue from where you actually left off, not from a hidden internal message.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}