{"version":"2.1.229","anchor":"remote-control-continue-is-documented-as-reattaching-not-res","canonical_anchor":"remote-control-continue-is-documented-as-reattaching-not-res","heading":"remote-control --continue is documented as reattaching, not resuming","tier":"use","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/remote-control-continue-is-documented-as-reattaching-not-res","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### remote-control --continue is documented as reattaching, not resuming\n\nRemote control's `--continue` is documented as reattaching to a session recorded in the last four hours.\n\n**What**\n\nThe help text for remote control now says `-c`\/`--continue` reattaches to the session last recorded for the current directory or one of its git worktrees, and errors if nothing was recorded in roughly the last 4 hours. `--session-id` is likewise described as reattaching.\n\n**Details**\n\n- Wording change only; the 4 hour window is now stated where before it was not.\n\n**Evidence**\n\n`Reattach to a specific session by ID (cannot be`\n\n- Area: Remote Control\n- Names: `--continue`, `-c`, `--session-id`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}