fix(desktop): deploy provider-backed agent updates - #5397
Draft
jvbutterfield wants to merge 1 commit into
Draft
Conversation
jvbutterfield
force-pushed
the
codex/remote-agent-update-deploy
branch
from
August 9, 2026 13:31
eafa2f0 to
3f7e7bc
Compare
Signed-off-by: Jason Butterfield <jbutterfield@gmail.com>
jvbutterfield
force-pushed
the
codex/remote-agent-update-deploy
branch
from
August 9, 2026 16:54
3f7e7bc to
3507b8c
Compare
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.
Summary
Fixes provider-backed managed-agent edits in Buzz Desktop.
The update command previously saved the revised Desktop record but did not call the provider's deploy operation. As a result, a remote agent kept its prior instruction and launch configuration even though the Desktop UI showed the edit as saved.
This change re-deploys the provider-backed agent after:
It keeps the provider deploy operation idempotent, so the remote launch configuration is updated without relying on a local Stop/Start transition that provider agents do not have.
Validation
just ci— completed locallyjust desktop-tauri-checkcargo test --manifest-path desktop/src-tauri/Cargo.toml agent_models --lib— 39 passedjust desktop-tauri-fmt-checkgit diff --checkUser impact
Editing a remote managed agent's instruction, model, harness, or policy now updates the remote provider immediately instead of leaving it running the prior configuration.