You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 15, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on May 15, 2026. It is now read-only.
[ENHANCEMENT] Add Checkpoints in the Orchestrator mode #10623
Right now, it is cumbersome to leverage Checkpoints feature from the Orchestrator mode's session view. As far as I can see, there are no Checkpoints created in this mode, however it is possible to reach into a subtask and try to revert from that place. But there are two problems with that: first, there's no easily accessible hierarchical navigation between subtasks (eg. going from parent by selecting specific subtask, and going back to parent from a subtask); and second, restoring from "not last" subtask is probably an error-prone action.
Context (who is affected and when)
Checkpoints in Orchestrator mode could be useful for situations where a subtask has been delegated, but ultimately the developer is not happy with the subtask's result (eg. the implementation is completely borked, and a different approach / prompt is necessary). With Checkpoints in Orchestrator, especially points created right before subtask delegation, it could be possible to restore to a place from before subtask delegation, effectively reverting that subtask's effects.
Desired behavior (conceptual, not technical)
When in Orchestrator mode, and when a subtask is being delegated - create a Checkpoint right before agent starts working on the subtask.
Later on, this Checkpoint should allow restoring both code and session conversation to the state from before the subtask has started.
As far as I can tell, when editing User messages in the Orchestrator mode, it offers a Checkpoint restore, therefore I suspect it should be possible to implement it on a subtask basis as well.
Request checklist
I've searched existing Issues and Discussions for duplicates
This describes a specific problem with clear context and impact
That's correct, I can't see any checkpoints being presented in the Orchestrator mode. The only way to access that feature directly in the Orchestrator mode is by providing "User messages" somewhere in session, and later on trying to "edit" that message - this way, Roo shows a modal asking the user whether they want to edit just the message, or restore to checkpoint and edit the message.
Both, but the behavior should be pickable by the user. This would be similar behavior to "edit message" feature I just mentioned in point 1.
Problem (one or two sentences)
Right now, it is cumbersome to leverage Checkpoints feature from the Orchestrator mode's session view. As far as I can see, there are no Checkpoints created in this mode, however it is possible to reach into a subtask and try to revert from that place. But there are two problems with that: first, there's no easily accessible hierarchical navigation between subtasks (eg. going from parent by selecting specific subtask, and going back to parent from a subtask); and second, restoring from "not last" subtask is probably an error-prone action.
Context (who is affected and when)
Checkpoints in Orchestrator mode could be useful for situations where a subtask has been delegated, but ultimately the developer is not happy with the subtask's result (eg. the implementation is completely borked, and a different approach / prompt is necessary). With Checkpoints in Orchestrator, especially points created right before subtask delegation, it could be possible to restore to a place from before subtask delegation, effectively reverting that subtask's effects.
Desired behavior (conceptual, not technical)
When in Orchestrator mode, and when a subtask is being delegated - create a Checkpoint right before agent starts working on the subtask.
Later on, this Checkpoint should allow restoring both code and session conversation to the state from before the subtask has started.
Constraints / preferences (optional)
Request checklist
Roo Code Task Links (optional)
No response
Acceptance criteria (optional)
No response
Proposed approach (optional)
No response
Trade-offs / risks (optional)
No response