{"version":"2.1.274","anchor":"fleet-view-background-agent-relaunch-can-now-target-a-specif","canonical_anchor":"fleet-view-background-agent-relaunch-can-now-target-a-specif","heading":"Fleet view background-agent relaunch can now target a specific agent type","tier":"use","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/fleet-view-background-agent-relaunch-can-now-target-a-specif","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Fleet view background-agent relaunch can now target a specific agent type\n\nFleet view can now relaunch a background agent as a specific agent type after an update\n\n**What**\n\nThe Fleet view (the screen listing background jobs\/agents) now accepts a `typedAgent` value, which flows through to the helper that relaunches the Fleet UI after an app update. When relaunching, this is passed via a new `--agent` argument, alongside the existing `cwdFilter` and `dispatchDefaults` (with an inherited default permission mode stripped out).\n\n**Why**\n\nThis lets a background agent relaunched after an update keep running as the specific agent type it was dispatched with, rather than losing that setting across the relaunch.\n\n- Area: Background Tasks\n- Names: `--agent`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}