Back to Signal Feed
CodeTracked since May 17, 2026

Prevent stale desktop Worker reuse during app upgrades

The PR updates local persistence recovery by version-gating Desktop-started Worker reuse. It now writes `appVersion` and `startedBy` into control-surface metadata, and Desktop launches only reuse a local Worker when that metadata shows the same launching app version; legacy or ownerless connection files are treated as stale and repaired before replacement Workers are started.

local Workercontrol-surface connection fileappVersionstartedBy

What Happened

  • The PR updates local persistence recovery by version-gating Desktop-started Worker reuse. It now writes `appVersion` and `startedBy` into control-surface metadata, and Desktop launches only reuse a local Worker when that metadata shows the same launching app version; legacy or ownerless connection files are treated as stale and repaired before replacement Workers are started.
  • The PR updates local persistence recovery by version-gating Desktop-started Worker reuse. It now writes `appVersion` and `startedBy` into control-surface metadata, and Desktop launches only reuse a local Worker when that metadata shows the same launching app version; legacy or ownerless connection files are treated as stale and repaired before replacement Workers are started.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Introduced explicit Worker ownership/version checks for Desktop launches (`appVersion` + `startedBy`) and added connection-file repair logic for stale or owner-missing records, so stale Desktop workers from prior app versions are no longer reused for the current session; CLI path is preserved via protocol-compatible reuse.

Why Track This

Why It Matters

Desktop users who upgrade the installed app should see more reliable workspace recovery instead of resuming into an old background process that can leave workspace data stale or missing, because the app now blocks cross-version Desktop Worker reuse and forces a clean recovery path when metadata is stale or incompatible. Concretely, this changes runtime selection from optimistic reuse to version-matched reuse for Desktop-started Workers, with old connection records repaired before replacement. Teams should watch mixed CLI/Desktop workflows for any regressions in cross-process handoff and verify lock/connection file repair remains robust after repeated upgrades and rollbacks.

Impact

Desktop users who upgrade the installed app should see more reliable workspace recovery instead of resuming into an old background process that can leave workspace data stale or missing, because the app now blocks cross-version Desktop Worker reuse and forces a clean recovery path when metadata is stale or incompatible. Concretely, this changes runtime selection from optimistic reuse to version-matched reuse for Desktop-started Workers, with old connection records repaired before replacement. Teams should watch mixed CLI/Desktop workflows for any regressions in cross-process handoff and verify lock/connection file repair remains robust after repeated upgrades and rollbacks.

What To Watch Next

  • Watch whether local Worker becomes a repeated pattern.
  • Track follow-up changes around AI IDE.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: desktop_upgrade_stale_worker_reuse, connection_file_repair_failures.
Open Topic TimelineOpen Technical EventOpen Original Sourcedesktop_upgrade_stale_worker_reuse / connection_file_repair_failures / cli_desktop_shared_userdata_edge_case

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

DeadWaveWave/opencove PR #264: Fix stale local worker reuse across app versions

Installed-app upgrades no longer attach Desktop to a previously started local Worker from another app version; stale local Worker records are repaired and replaced.