[GH-ISSUE #387] Bash operations don't appear as AI edit #143

New issue

Open

opened 2026-03-02 04:12:14 +03:00 by kerem · 1 comment

kerem commented

2026-03-02 04:12:14 +03:00

Owner

Originally created by @divaltor on GitHub (Jan 21, 2026).
Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/387

Hello, thanks for this interesting CLI. I've noticed that when the Agent deletes a file using Bash operations, the subsequent commit attributes the change to the user (human) rather than the AI.

I understand that tracking changes made via shell commands is difficult. However, could we implement tracking using hooks similar to those used in OpenCode or other CLI tools to ensure AI actions are correctly attributed?

I didn't research could we do it using hooks or not, but leave it as proposal for now

git-ai version: 1.0.36
opencode version: 1.0.28

Originally created by @divaltor on GitHub (Jan 21, 2026). Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/387 Hello, thanks for this interesting CLI. I've noticed that when the Agent deletes a file using Bash operations, the subsequent commit attributes the change to the user (human) rather than the AI. I understand that tracking changes made via shell commands is difficult. However, could we implement tracking using hooks similar to those used in OpenCode or other CLI tools to ensure AI actions are correctly attributed? I didn't research could we do it using hooks or not, but leave it as proposal for now git-ai version: 1.0.36 opencode version: 1.0.28 <img width="745" height="246" alt="Image" src="https://github.com/user-attachments/assets/0de03838-b7e9-474c-844b-4cc2ab9eed9e" /> <img width="923" height="138" alt="Image" src="https://github.com/user-attachments/assets/c6cd2fc7-1096-4dbf-900c-5562a13907aa" />

kerem added the

enhancement

label

2026-03-02 04:12:14 +03:00

kerem commented

2026-03-02 04:12:15 +03:00

Author

Owner

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

This is a great point. As a 80/20 solution, it wouldn't be hard to come up with some heuristics for this and update our hooks to also be notified on shell tool calls. The thing is we have to be smart about this -- we can't just run git status on every tool call or watch the file system as it's way too taxing on large repos and a big focus of the Git AI project is performance so good that it's not even noticeable.

@svarlamov commented on GitHub (Jan 21, 2026): This is a great point. As a 80/20 solution, it wouldn't be hard to come up with some heuristics for this and update our hooks to also be notified on shell tool calls. The thing is we have to be smart about this -- we can't just run `git status` on every tool call or watch the file system as it's way too taxing on large repos and a big focus of the Git AI project is performance so good that it's not even noticeable.

kerem referenced this issue

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

[PR #143] Fix linux builds #283