{"version":"2.1.281","anchor":"continue-records-the-resume-source-cloud-attach-forwards","canonical_anchor":"continue-records-the-resume-source-cloud-attach-forwards","heading":"--continue records the resume source; cloud attach forwards added directories","tier":"notice","area":"Resume","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/continue-records-the-resume-source-cloud-attach-forwards","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### --continue records the resume source; cloud attach forwards added directories\n\n--continue now records where a resumed session came from, and attaching to a cloud session passes on extra working directories\n\n**Unclear.** The finding does not say what recording `resumeSource: \"store\"` changes for someone using `--continue`.\n\n**What**\n\nThree changes around resuming and cloud sessions:\n\n- `--continue`, the option that reopens your most recent conversation in the current directory, now records `resumeSource: \"store\"`.\n\n- Attaching to a cloud session, meaning a session running on a remote machine, now passes your extra working directories (`additionalWorkingDirectories`) to the fleet view that opens afterwards, as `dispatchExtraArgs`.\n\n- The `tengu_remote_create_session` record gains a `disallowed_tools_count` field. In this build the value it reads from is never filled in, so the new `deny_rule_unclosed` error cannot occur.\n\n**Why**\n\nFolders you are working in beyond the main one now travel with you into the view you get after attaching to a cloud session. The tool-count field and its error are present but have no effect yet.\n\n- Area: Resume\n- Names: `--continue`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}