feat: add tess retry <agent> command#7
Open
vibhu-dixit wants to merge 2 commits into
Open
Conversation
Re-run a dead or failed agent in the same worktree with the same prompt, tool, model, and budget — the natural recovery-from-failure button after spawn/watch/status. What is recovered automatically: - tool (claude / kimi) from hcom list - worktree (agent's working directory) from hcom list - tag from hcom list - model and budget cap from ~/.config/tess/state/budgets.json - prompt: first user message from the agent's transcript Role flags (--readonly / --auto / --can-deploy) are not stored at spawn time and must be re-supplied if needed. The old registered agent is killed first so a fresh name registers cleanly in the same tag group. Changes: - bin/_tess-retry.py new command implementation - bin/tess menu entry, dispatch case, reserved word - bin/_tess-help.sh tess help retry entry with all flags documented
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.
Re-run a dead or failed agent in the same worktree with the same prompt, tool, model, and budget — the natural recovery-from-failure button after spawn/watch/status.
Closes #6
What is recovered automatically:
Role flags (--readonly / --auto / --can-deploy) are not stored at spawn time and must be re-supplied if needed.
The old registered agent is killed first so a fresh name registers cleanly in the same tag group.
Changes: