Skip to content

Conversation

evanliu048
Copy link
Contributor

@evanliu048 evanliu048 commented Sep 27, 2025

Issue #, if available:

Description of changes:

  • Updated git command handling: now correctly use the current working directory as work tree, fixing potential path issues and avoiding potential inconsistencies.

  • Added explicit error handling for cases where git add -A fails.

  • Always unlock message_locked at the end of a turn (with or without tools). This ensures we reliably capture the first natural-language message of each turn and release the lock consistently.

  • Improved CLI help text for checkpoint commands.
    By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

kiran-garre and others added 30 commits August 13, 2025 16:48
Updates:
- Only works if the user has git installed
- Supports auto initialization if the user is in a git repo, manual
if not
- UI ported over from dedicated file tools implementation
Updates:
- The clean subcommand will delete the shadow repo
- The description for turn-level checkpoints is a truncated version
of the user's last message
Updates:
- Running the clean subcommand now properly deletes the entire
shadow repo for both automatic and manual modes
Updates:
- Users can now view diffs between checkpoints
- Fixed tool-level checkpoint display handling
Updates:
- Checkpoints now (hopefully) correctly display the correct
turn-specific user message
- Added slash command auto completion
@evanliu048
Copy link
Contributor Author

CI failure is unrelated to this PR

@kensave
Copy link
Contributor

kensave commented Sep 29, 2025

I think this branch needs a rebase.

@kensave
Copy link
Contributor

kensave commented Sep 29, 2025

CI failure is unrelated to this PR

Can we fix the formatting?

Comment on lines +417 to +423
if !output.stderr.is_empty() {
bail!("Git command failed: {}", String::from_utf8_lossy(&output.stderr));
} else {
bail!(
"Git command failed with no error output. Command: git {}",
args.join(" ")
);
Copy link
Contributor

Choose a reason for hiding this comment

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

Does the user care about which git command failed? IOW, the error message we show to users should be something related to checkpoint feature, rather than git-commands

Copy link
Contributor

@kkashilk kkashilk left a comment

Choose a reason for hiding this comment

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

Just one comment about the message we show to users

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants