After `!shutdown` there is no way to redeploy from the UI
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust, typescript
Research direction
Start in managed_agents/runtime.rs and trace how backend_agent_id and the derived status change after !shutdown. Then inspect features/agents/lib/managedAgentControlActions.ts and the remote-backend filtering in managed_agents/runtime_commands.rs. Done means a remotely managed agent can return from graceful shutdown to a working Deploy or Redeploy path without manually clearing backend_agent_id.
Written by the indexing model from the issue text.
Description
Severity: medium — a dead end.
managed_agents/runtime.rs derives the control-plane status from
backend_agent_id:
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):
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.
- Dominant language
- Rust
- Stars
- 33.7k
- Forks
- 4.4k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 239
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from block/buzz
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
workflow_sink's mention parser never masks code regions — @name inside a code span wakes the agent Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 Half a day Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100