#7724·buzz

After `!shutdown` there is no way to redeploy from the UI

Author: meeveemCreated Sep 18, 2026Updated Sep 18, 2026

Severity: medium — a dead end.

managed_agents/runtime.rs derives the control-plane status from backend_agent_id:

rust
let status = if record.backend_agent_id.is_some() { "deployed" } else { "not_deployed" };

with the comment "After !shutdown the agent goes offline (presence) but stays 'deployed' (infrastructure still exists). This is intentional … A future provider undeploy operation (v2) will handle teardown."

But the UI uses that status to pick the button (features/agents/lib/managedAgentControlActions.ts):

javascript
if (agent.backend.type === "provider") {
  return isManagedAgentActive(agent) ? "Shutdown" : "Deploy";
}

So after a graceful shutdown the only button is Shutdown, and it does nothing. There is no path back to Deploy. Clearing backend_agent_id by hand is the only workaround.

Expected: either a Deploy/Redeploy action while deployed but offline, or clear backend_agent_id when the harness exits.

Related: start_on_app_launch is filtered to local backends (managed_agents/runtime_commands.rs), so remote agents never auto-deploy on app launch either.