Skip to content

fix: restore checkpoint visibility in UI #7787

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

fix: restore checkpoint visibility in UI #7787

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/core/task/Task.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -892,9 +892,9 @@ export class Task extends EventEmitter<TaskEvents> implements TaskLike {

// Create a checkpoint whenever the user sends a message.
// Use allowEmpty=true to ensure a checkpoint is recorded even if there are no file changes.
// Suppress the checkpoint_saved chat row for this particular checkpoint to keep the timeline clean.
// Do not suppress the checkpoint_saved chat row so users can see and restore checkpoints.
Copy link
Contributor Author

@roomote roomote bot Sep 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch on updating the comment to match the new behavior. This makes the intent clear for future maintainers.

if (askResponse === "messageResponse") {
void this.checkpointSave(false, true)
void this.checkpointSave(false, false)
Copy link
Contributor Author

@roomote roomote bot Sep 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the correct fix. Changing from true to false ensures checkpoint messages are visible in the UI, which directly addresses the issue reported in #7786.

However, would it be worth adding a test case specifically for this behavior? Something that verifies checkpointSave is called with suppressMessage=false when handling messageResponse. This would help prevent regression in the future.

}

// Mark the last follow-up question as answered
Expand Down
Loading