starred/git-ai

Fork 0

mirror of https://github.com/git-ai-project/git-ai.git synced 2026-04-25 14:25:53 +03:00

[GH-ISSUE #305] VS Code extension checkpoints failing #110

New issue

Closed

opened 2026-03-02 04:11:52 +03:00 by kerem · 8 comments

kerem commented

2026-03-02 04:11:52 +03:00

Owner

Originally created by @miguelelvir on GitHub (Dec 23, 2025).
Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/305

Hi!
First, let me say how thrilled I am to see a product tackle this need. Thank you for your work on it. I'd like to report a bug in a Windows 11 VS Code + Github Copilot setup:

When the Copilot agent tries to edit any files, I see the above image. The logs show:

[error] [Window] [Extension Host] [git-ai] AIEditManager: Checkpoint exited with code: 1  Checkpoint failed after 134.3383ms with error IO error: trailing characters at line 1 column 7859

The result is no notes being saved.

Thank you for your kind effort on this project.

Originally created by @miguelelvir on GitHub (Dec 23, 2025). Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/305 Hi! First, let me say how thrilled I am to see a product tackle this need. Thank you for your work on it. I'd like to report a bug in a Windows 11 VS Code + Github Copilot setup: <img width="917" height="278" alt="Image" src="https://github.com/user-attachments/assets/2deb5ee5-7030-462c-bab7-f810c7f370ce" /> When the Copilot agent tries to edit any files, I see the above image. The logs show: ```text [error] [Window] [Extension Host] [git-ai] AIEditManager: Checkpoint exited with code: 1 Checkpoint failed after 134.3383ms with error IO error: trailing characters at line 1 column 7859 ``` The result is no notes being saved. Thank you for your kind effort on this project.

kerem closed this issue

2026-03-02 04:11:53 +03:00

kerem commented

2026-03-02 04:11:54 +03:00

Author

Owner

@miguelelvir commented on GitHub (Dec 23, 2025):

Further details:

Running on a local branch for the agent work
git-ai diff master returned a different set of changed files (this was on a fresh clone of a repo). It seems to have returned the diff from a previous commit on the main branch.
Running git-ai checkpoint --reset cleared the extra files. Now the checkpoints work

Found a workaround thanks to: https://usegitai.com/docs/reference#plumbing-commands-for-ai-agents
Thanks for the docs!
Hopefully this helps to continue improving it.

@miguelelvir commented on GitHub (Dec 23, 2025): Further details: * Running on a local branch for the agent work * `git-ai diff master` returned a different set of changed files (this was on a fresh clone of a repo). It seems to have returned the diff from a previous commit on the main branch. * Running `git-ai checkpoint --reset` cleared the extra files. Now the checkpoints work Found a workaround thanks to: https://usegitai.com/docs/reference#plumbing-commands-for-ai-agents Thanks for the docs! Hopefully this helps to continue improving it.

kerem commented

2026-03-02 04:11:54 +03:00

Author

Owner

@miguelelvir commented on GitHub (Dec 23, 2025):

Will reopen the issue with a few observations, but feel free to close as needed:

After letting the agent do all the work, it reports only 58% of the code as coming from AI. I would have expected 100% since it was on autopilot. Doing a quick git-ai diff master again, it showed diffs from a commit that was not from the current session. That commit was 100% human. My guess is that the extra data there skews the results and perhaps is related to the same checkpoint error.

/cc @acunniffe

@miguelelvir commented on GitHub (Dec 23, 2025): Will reopen the issue with a few observations, but feel free to close as needed: <img width="1377" height="298" alt="Image" src="https://github.com/user-attachments/assets/4817408e-5753-4025-943c-24cc6a37bde6" /> After letting the agent do all the work, it reports only 58% of the code as coming from AI. I would have expected 100% since it was on autopilot. Doing a quick `git-ai diff master` again, it showed diffs from a commit that was not from the current session. That commit was 100% human. My guess is that the extra data there skews the results and perhaps is related to the same checkpoint error. /cc @acunniffe

kerem commented

2026-03-02 04:11:54 +03:00

Author

Owner

@miguelelvir commented on GitHub (Dec 23, 2025):

I enabled the notifications on VS Code and see two checkpoints (one human and one ai) triggered when editing files:

Likely related to the overall stats.

@miguelelvir commented on GitHub (Dec 23, 2025): I enabled the notifications on VS Code and see two checkpoints (one human and one ai) triggered when editing files: <img width="958" height="263" alt="Image" src="https://github.com/user-attachments/assets/754897a3-951a-4f54-8360-5a1f42593d8a" /> Likely related to the overall stats.

kerem commented

2026-03-02 04:11:54 +03:00

Author

Owner

@acunniffe commented on GitHub (Dec 23, 2025):

Hey thanks for the kind words. saw you closed this!

If you need help debugging more feel free to grab one of us https://calendly.com/acunniffe/meeting-with-git-ai-authors

@acunniffe commented on GitHub (Dec 23, 2025): Hey thanks for the kind words. saw you closed this! If you need help debugging more feel free to grab one of us https://calendly.com/acunniffe/meeting-with-git-ai-authors

kerem commented

2026-03-02 04:11:54 +03:00

Author

Owner

@miguelelvir commented on GitHub (Dec 23, 2025):

Hey thanks for the kind words. saw you closed this!

If you need help debugging more feel free to grab one of us https://calendly.com/acunniffe/meeting-with-git-ai-authors

Thanks so much! I might take you up on that. Still trying to determine if triggering the two checkpoints when the AI edits files is expected.

@miguelelvir commented on GitHub (Dec 23, 2025): > Hey thanks for the kind words. saw you closed this! > > If you need help debugging more feel free to grab one of us https://calendly.com/acunniffe/meeting-with-git-ai-authors Thanks so much! I might take you up on that. Still trying to determine if triggering the two checkpoints when the AI edits files is expected.

kerem commented

2026-03-02 04:11:54 +03:00

Author

Owner

@svarlamov commented on GitHub (Dec 23, 2025):

Hey Miguel! Happy to chime in here. Thanks for enabling the debug mode in the extension. Seeing the two checkpoints (human, followed by AI) is the expected behavior. Git AI first runs a human checkpoint to mark the state of the file before the AI change, and finally the AI checkpoint runs to associate the new change with that AI agent.

Couple thoughts on the human vs AI commit stats.

I noticed the commit message is something about updating .NET -- are there any changes in package manager files or something of that sort? Any changes to lockfiles, etc. that are driven by package managers come through as human edits. Git AI only captures what the agent literally wrote on it's own, even if the package manager was invoked by the AI.
Are things working as expected now if you run git reset head --hard and then make some AI changes? It's hard to tell just from our thread so far whether or not the stats might've been impacted by the earlier issues with checkpoints.
Are you able to replicate the checkpoint IO error from your initial report?

@svarlamov commented on GitHub (Dec 23, 2025): Hey Miguel! Happy to chime in here. Thanks for enabling the debug mode in the extension. Seeing the two checkpoints (human, followed by AI) is the expected behavior. Git AI first runs a human checkpoint to mark the state of the file before the AI change, and finally the AI checkpoint runs to associate the new change with that AI agent. Couple thoughts on the human vs AI commit stats. 1. I noticed the commit message is something about updating .NET -- are there any changes in package manager files or something of that sort? Any changes to lockfiles, etc. that are driven by package managers come through as human edits. Git AI only captures what the agent literally wrote on it's own, even if the package manager was invoked by the AI. 2. Are things working as expected now if you run `git reset head --hard` and then make some AI changes? It's hard to tell just from our thread so far whether or not the stats might've been impacted by the earlier issues with checkpoints. 3. Are you able to replicate the checkpoint IO error from your initial report?

kerem commented

2026-03-02 04:11:54 +03:00

Author

Owner

@svarlamov commented on GitHub (Dec 29, 2025):

@miguelelvir Just wanted to check in if you had a chance to try replicating the issue?

@svarlamov commented on GitHub (Dec 29, 2025): @miguelelvir Just wanted to check in if you had a chance to try replicating the issue?

kerem commented

2026-03-02 04:11:54 +03:00

Author

Owner

@svarlamov commented on GitHub (Jan 6, 2026):

@miguelelvir Happy new year! Just wanted to check in if you're still seeing this issue before I close the issue

@svarlamov commented on GitHub (Jan 6, 2026): @miguelelvir Happy new year! Just wanted to check in if you're still seeing this issue before I close the issue