feat(agent): add stop/start to free cluster resources#3
Merged
Conversation
Restart only redeployed the pod, so there was no way to free a slot on a full cluster. Add a true Stop (cancel workflow + delete pod, keep the agent as `stopped`) and a paired Start (deploy a fresh pod). Backend: - POST /agents/:id/stop and /agents/:id/start (Owner/Admin) - AgentDeployService.stopAgent() with deploy-tracker guard so the dying pod's Failed event can't flip the row to `failed` - reconciler ignores a stale Running event for a stopped/restarting agent - syncStatus skips `stopped`; updateStatus can clear workflowId via null Admin UI: - Stop/Start in the agents table row dropdown - Stop/Start in the agent detail header (top-right) + a "stopped" chat overlay with a Start button Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Restart only redeployed the pod, so there was no way to free a slot on a full cluster. Add a true Stop (cancel workflow + delete pod, keep the agent as
stopped) and a paired Start (deploy a fresh pod).Backend:
failedstopped; updateStatus can clear workflowId via nullAdmin UI: