{"version":"2.1.247","anchor":"aborted-workspace-diff-requests-are-reused-for-60-seconds","canonical_anchor":"aborted-workspace-diff-requests-are-reused-for-60-seconds","heading":"Aborted workspace-diff requests are reused for 60 seconds","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/aborted-workspace-diff-requests-are-reused-for-60-seconds","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Aborted workspace-diff requests are reused for 60 seconds\n\nCancelling a workspace diff and asking again within a minute reuses the finished result instead of recomputing.\n\n**What**\n\nConcurrent workspace-diff requests now share a single computation, keyed on the current tool permission context. If every waiter aborts before it finishes, the result is kept and handed to the next request within 60000 ms, so cancelling a diff on your phone and asking again does not recompute it from scratch.\n\n**Details**\n\n- The handler is registered only when the caller supplies a session host; without one the control request still fails with \"not supported in this context\".\n- A new workspace-diff compute budget is threaded from the app host into the diff computation.\n\n**Evidence**\n\n`workspaceDiffComputeBudget`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}