Switch the PR's model
Two follow-ups in, the same bug survives. Comment /switch with a configured model, and every later comment, command and Ultrafix cycle on the PR runs on it.
On its own, /switch changes the model and touches no code.
One comment replaces a model that keeps missing the point. One click, with a preview, removes a follow-up that went the wrong way. Both happen on the PR, and the next comment carries on from there.
Two follow-ups in, the same bug survives. Comment /switch with a configured model, and every later comment, command and Ultrafix cycle on the PR runs on it.
On its own, /switch changes the model and touches no code.
Lines below the command become a follow-up for the new model.
/switch claude-fable51
The retry still races the timeout. Serialize the two paths and add a test that reproduces the race.
Want one run from another model and then the old one back? /use does that run; the PR keeps its model.
Every follow-up completion comment carries an Undo Changes link for its commit. It opens a preview in ProPR before anything moves.
Applied the follow-up. Moved the order summary below the form on phones.
The preview names the commit that becomes the new head and every commit that goes.
ProPR returns the PR branch to the new head. From the terminal, propr task revert does the same, with --dry-run for the preview.
/switchThe model is wrong for this PR. The new one takes every later run.
/useYou want a second opinion on one run. The PR keeps its model.
The last follow-up made things worse. The branch goes back to the commit before it.
See every command in GitHub comment control.
You hand a stuck PR to another model, or return the branch to where it was before the last follow-up, and ProPR records both on the PR.
/switch codex-astra