[GH-ISSUE #544] Codex implementation marks newly created files as 100% human-edited #182

Open
opened 2026-03-02 04:12:39 +03:00 by kerem · 4 comments
Owner

Originally created by @xavierutox on GitHub (Feb 17, 2026).
Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/544

When a new file is generated using Codex, the file is incorrectly reported as 100% human-edited.
The AI/Human contribution percentage is only correctly calculated for existing files that are modified, but not for newly created files.

In contrast, with the Copilot implementation, newly generated files are correctly labeled with the appropriate AI contribution percentage.

Steps to Reproduce

  • Ask Codex to generate a new file.
  • Run git-ai status.

Expected Behavior

  • Newly generated files should be reported as 100% AI-generated, or reflect the correct AI contribution percentage.

Actual Behavior

  • Newly generated files are marked as 100% human-edited.
Originally created by @xavierutox on GitHub (Feb 17, 2026). Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/544 When a new file is generated using Codex, the file is incorrectly reported as 100% human-edited. The AI/Human contribution percentage is only correctly calculated for existing files that are modified, but not for newly created files. In contrast, with the Copilot implementation, newly generated files are correctly labeled with the appropriate AI contribution percentage. Steps to Reproduce * Ask Codex to generate a new file. * Run git-ai status. Expected Behavior * Newly generated files should be reported as 100% AI-generated, or reflect the correct AI contribution percentage. Actual Behavior * Newly generated files are marked as 100% human-edited.
Author
Owner

@svarlamov commented on GitHub (Feb 17, 2026):

Hey @xavierutox sorry to hear you're running into attribution issues with codex!

Could you help me gather some more data:

  1. Are you using the codex CLI, GUI, or background agent?
  2. What are the exact version(s) of codex that you're using? Codex only recently shipped hooks support so most likely issue is a version mismatch.
  3. What is the output of git-ai install-hooks?
  4. What is your git-ai version (git-ai version)?

Thanks!

<!-- gh-comment-id:3916475228 --> @svarlamov commented on GitHub (Feb 17, 2026): Hey @xavierutox sorry to hear you're running into attribution issues with codex! Could you help me gather some more data: 1. Are you using the codex CLI, GUI, or background agent? 2. What are the exact version(s) of codex that you're using? Codex only recently shipped hooks support so most likely issue is a version mismatch. 3. What is the output of `git-ai install-hooks`? 4. What is your git-ai version (`git-ai version`)? Thanks!
Author
Owner

@xavierutox commented on GitHub (Feb 17, 2026):

Hey! Thanks for the response.

I'm testing with both the CLI (v0.101.0) and the VS Code plugin (v0.5.75 pre-release) on Windows + WSL.

`$ git-ai install-hooks

Coding Agents
✓ Claude Code: Hooks already up to date
✓ Codex: Hooks already up to date
✓ VS Code: Hooks already up to date
✓ VS Code: Extension already installed

Git Clients`

$ git-ai version 1.1.3

I ran additional tests with just the CLI

Changes to an existing file:

Image

New file:

Image
<!-- gh-comment-id:3916589409 --> @xavierutox commented on GitHub (Feb 17, 2026): Hey! Thanks for the response. I'm testing with both the CLI (v0.101.0) and the VS Code plugin (v0.5.75 pre-release) on Windows + WSL. `$ git-ai install-hooks Coding Agents ✓ Claude Code: Hooks already up to date ✓ Codex: Hooks already up to date ✓ VS Code: Hooks already up to date ✓ VS Code: Extension already installed Git Clients` `$ git-ai version 1.1.3` I ran additional tests with just the CLI Changes to an existing file: <img width="937" height="795" alt="Image" src="https://github.com/user-attachments/assets/987aa647-344f-4819-a0d4-f21668febfdf" /> New file: <img width="939" height="577" alt="Image" src="https://github.com/user-attachments/assets/719d888b-0c4d-4940-a242-7ccdafc7629b" />
Author
Owner

@svarlamov commented on GitHub (Feb 17, 2026):

Versions all look correct, and from the screenshots it looks like it's actually working, right? git-ai status can be kind of flaky, what %'s do you get if you git commit

<!-- gh-comment-id:3917443168 --> @svarlamov commented on GitHub (Feb 17, 2026): Versions all look correct, and from the screenshots it looks like it's actually working, right? `git-ai status` can be kind of flaky, what %'s do you get if you `git commit`
Author
Owner

@svarlamov commented on GitHub (Feb 18, 2026):

I have definitely noticed some issues with the codex integration being flaky. I'm investigating

<!-- gh-comment-id:3921595559 --> @svarlamov commented on GitHub (Feb 18, 2026): I have definitely noticed some issues with the codex integration being flaky. I'm investigating
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/git-ai#182
No description provided.