{"version":"2.1.304","anchor":"remote-workflow-runs-are-now-synced-into-the-thin-client-and","canonical_anchor":"remote-workflow-runs-are-now-synced-into-the-thin-client-and","heading":"Attached sessions now receive workflow runs started elsewhere","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/remote-workflow-runs-are-now-synced-into-the-thin-client-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Attached sessions now receive workflow runs started elsewhere\n\nWhen you attach to a remote session, Claude Code now syncs its workflow runs as well as its background tasks\n\n**What**\n\nAttaching means connecting your Claude Code window to a session that is running somewhere else. Before, only that session's background tasks were synced to your window.\n\nWorkflow runs are now synced as well:\n\n- On attach, they are filled in from the session's snapshot.\n\n- While you stay connected, they are kept up to date.\n\n- When you disconnect, they are cleared.\n\n**Why**\n\nAn attached session can now show workflow runs that were started from another place, not only its background tasks.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}