Thanks for the warning. Can you share more details about what actually happened?

I've seen some issues with AI coding assistants before, but "seriously damage your codebase" is pretty broad. What exactly did Git AI Codex do? Did it delete code, introduce bugs, overwrite files it shouldn't have, or something else?

Also, what do you mean by "context size grows larger"? Are you talking about a large codebase, a long chat history, or something specific to how the tool works?

I'm not defending the team here, but without concrete examples it's hard to know if this is a real flaw in the tool, a misuse case, or something else entirely.

If you have logs, screenshots, or a step-by-step of what happened, that would help everyone else avoid the same issue.

And yeah, support going silent is frustrating. Been there. But calling it a "lack of professional ethics" is a strong claim. Do you have any response from them at all, or just no reply yet?

Hi @longdaukhac,

I completely understand your frustration. It is incredibly stressful when an automated tool behaves unpredictably on a large codebase, and waiting for support while things are broken only adds to that stress.

To echo @miladrezanezhad's excellent questions above, having concrete examples or logs would really help the community understand the exact bug you are hitting.

Regarding the issue of the AI making mistakes as the "context size grows larger": this is actually a well-known limitation across almost all current Large Language Models (LLMs), not just this specific tool. It's often referred to as "context degradation" or "hallucination." When the context window gets completely filled, the AI struggles to maintain the correct state of the entire codebase and might overwrite things incorrectly, forget earlier instructions, or introduce logical errors. It is a fundamental limitation of current AI architectures.

A quick safety reminder for everyone using AI coding assistants:
The absolute best defense against AI hallucinations is relying on your version control. AI tools are "co-pilots," not autonomous developers yet.

Never skip the review: Always check the diffs carefully before accepting large AI-generated changes.

Commit frequently: Commit your working, stable state before asking the AI to do a massive refactor or generate a lot of code.

Rollback: Because you are using Git, an AI cannot permanently "damage" your codebase. If it messes up, a simple git reset --hard or discarding the changes in your IDE will revert the damage instantly.

If you are able to share the specific nature of the corruption (e.g., did it silently delete functions, mess up imports, or change core logic?), it would be highly valuable for the rest of us so we know what specific behaviors to watch out for!

I was about to say. Who lets random typed things in a not backedup environment?
You even are on GIT-Hub, a place to backup your history...