{"version":"2.1.257","anchor":"background-worker-retirement-gains-version-staleness-path-wi","canonical_anchor":"background-worker-retirement-gains-version-staleness-path-wi","heading":"Background worker retirement gains version-staleness path with new causes","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/background-worker-retirement-gains-version-staleness-path-wi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Background worker retirement gains version-staleness path with new causes\n\nA background worker can now be retired purely for running a stale CLI version, with new retirement causes recorded.\n\nThe background-agent worker manager can now retire a worker purely because its CLI version is stale (`this.isVersionStale`), even when the worker isn't idle, as long as it isn't running `session_cron`, isn't a routine, has no in-flight tasks or queue, and its last update predates a threshold (`BMe`). The `tengu_bg_retired` telemetry event gains a `cause` field with values including `abandoned-stale`, `settled`, `idle-prompt`, and `empty-idle`, plus a `worker_cli_version` field.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}