fix(coding-agent): revive tombstoned workers on retry - #836
Merged
Conversation
This was referenced Aug 7, 2026
alexzhang13
approved these changes
Aug 7, 2026
snimu
added a commit
that referenced
this pull request
Aug 7, 2026
Patch release. Bug fixes only, no breaking changes, per the no-major-releases policy. Contents since v0.7.0: - #836 retry_worker clears saved stop markers so retried workers recover - #809 websearch skill documents the /login -> MCP Connections Serper step - #699 dropped Nemotron 3 Ultra from the Prime Inference catalog - #658/#661/#700/#787 test, comment, and README maintenance (no user-facing behavior) Lockstep bump across the root package and the four published packages; example and private workspaces untouched. Lockfile updated surgically (version fields and inter-package ranges only).
zhengr
pushed a commit
to zhengr/prime-agent
that referenced
this pull request
Aug 8, 2026
zhengr
pushed a commit
to zhengr/prime-agent
that referenced
this pull request
Aug 8, 2026
Patch release. Bug fixes only, no breaking changes, per the no-major-releases policy. Contents since v0.7.0: - PrimeIntellect-ai#836 retry_worker clears saved stop markers so retried workers recover - PrimeIntellect-ai#809 websearch skill documents the /login -> MCP Connections Serper step - PrimeIntellect-ai#699 dropped Nemotron 3 Ultra from the Prime Inference catalog - PrimeIntellect-ai#658/PrimeIntellect-ai#661/PrimeIntellect-ai#700/PrimeIntellect-ai#787 test, comment, and README maintenance (no user-facing behavior) Lockstep bump across the root package and the four published packages; example and private workspaces untouched. Lockfile updated surgically (version fields and inter-package ranges only).
okwilkins
pushed a commit
to okwilkins/prime-agent
that referenced
this pull request
Aug 10, 2026
okwilkins
pushed a commit
to okwilkins/prime-agent
that referenced
this pull request
Aug 10, 2026
okwilkins
pushed a commit
to okwilkins/prime-agent
that referenced
this pull request
Aug 10, 2026
okwilkins
pushed a commit
to okwilkins/prime-agent
that referenced
this pull request
Aug 12, 2026
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
2 participants
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.
What broke
A stopped session worker can leave a saved stop marker behind. Running
retry_workercleared the in-memory stop flag, but not the saved marker, so recovery immediately cancelled itself. The session then stayed unavailable with:Fix
When the user explicitly retries a worker, clear its saved stop markers before starting recovery. This matches the existing recovery behavior for client-owned workers.
Scope
This only changes the explicit
retry_workerpath. Automatic recovery and normal stop behavior are unchanged. There is no daemon protocol change.Validation
daemon-supervisor-monitor.test.ts: 43 tests passed.npm run checkpassed.