fix(desktop): let owners deploy remote agents again - #7485
Open
FabianHertwig wants to merge 1 commit into
Open
Conversation
Expose an explicit Deploy again action for retained provider deployments. Reuse the existing same-identity provider handoff while keeping Shutdown and relay presence independent. Exercise failure and retry through the rendered profile. Implemented by Chatty; configured attribution authorized by Fabian in the originating Buzz conversation. Signed-off-by: Fabian Hertwig <fabian.hertwig@gmail.com>
🔐 Codex Security Review
|
FabianHertwig
marked this pull request as ready for review
September 8, 2026 15:19
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
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.
An owned remote agent whose sandbox has ended retains
status=deployed, so its profile offers only Shutdown. Add an explicit Deploy again action that repeats the existing provider handoff for the same identity. Keep Shutdown and relay presence independent; provider idempotency decides whether to reuse a live instance or create a replacement.The profile now reports that deployment was requested instead of claiming a process restarted. Local restart behavior and owner gates stay unchanged.
Validation: 6,450 desktop tests passed; E2E build and all 12 agent-availability profile tests passed, including provider failure, retry, the same public key, and no stop/delete/create call. The rendered offline profile was visually checked. Repository-wide
just cireached two ACP default-value failures caused by inheritedBUZZ_ACP_LAZY_POOL/BUZZ_ACP_IDLE_POOL_SLEEP; the complete ACP package passed without these variables (919 unit and 9 integration tests). All remaining CI stages passed separately, including Tauri tests, desktop/web builds, and all 2,076 mobile tests. The installed production desktop app remains unchanged.Originating Buzz channel: 5439dabc-5146-48f2-8cac-75652fc3da97.