{"version":"2.1.247","anchor":"remote-clients-can-now-get-a-whole-workspace-diff-from-a-ter","canonical_anchor":"remote-clients-can-now-get-a-whole-workspace-diff-from-a-ter","heading":"Remote clients can now get a whole-workspace diff from a terminal session","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/remote-clients-can-now-get-a-whole-workspace-diff-from-a-ter","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Remote clients can now get a whole-workspace diff from a terminal session\n\nViewing a terminal session remotely can now show a whole-workspace diff instead of a version-mismatch message.\n\n**What**\n\nA remote viewer asking a terminal session for a workspace-wide diff used to get the \"older Claude Code version\" fallback, because only the SDK path could answer. The terminal session now serves it, with per-file and total compute budgets, a short-lived cache of the result, and an 8 second deadline after which a new timeout message is returned.\n\n**Details**\n\n- The terminal now hands the bridge the session host plus a compute budget; the diff handler registers only when that host is present.\n- No feature flag on the handler itself, so it is reachable for anyone using Remote Control on this build.\n\n**Evidence**\n\n`get_workspace_diff is not supported in this context (onGetWorkspaceDiff callback not registered)`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}