{"version":"2.1.304","anchor":"remote-session-reported-cwd-tracking-and-rate-limit-hold-ha","canonical_anchor":"remote-session-reported-cwd-tracking-and-rate-limit-hold-ha","heading":"Remote sessions report their working folder and track workflow runs","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/remote-session-reported-cwd-tracking-and-rate-limit-hold-ha","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Remote sessions report their working folder and track workflow runs\n\nRemote sessions now report their working folder once, follow it differently, and track workflow runs until you disconnect\n\n**What**\n\nA remote session is a Claude Code session that runs on another machine while you work with it from your own. Such a session now reports its working directory (the folder its commands run in) once, and the way it follows that reported folder has changed.\n\nRemote sessions also keep track of workflow runs. The runs are recorded when the session is set up and followed as they go. Disconnecting clears them.\n\n**Why**\n\nRemote and web sessions now behave a little differently from each other in how they handle the working folder and running workflows.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}