> AI slop nothing burger. The “exploit” has nothing to do with coding agents.
It's pretty small potatoes, but it is a harness ~bug that they treat this so poorly. It getting triggered before some of them even ask you if you trust the directory is pretty bad.
> Git reads that setting from the repository's own .git/config. So a repository can ship this:
Followed by:
> Delivery is worth being precise about, because git never carries this. Cloning a hostile URL does nothing, and neither does fetch or pull.
AI slop nothing burger. The “exploit” has nothing to do with coding agents.
> AI slop nothing burger. The “exploit” has nothing to do with coding agents.
It's pretty small potatoes, but it is a harness ~bug that they treat this so poorly. It getting triggered before some of them even ask you if you trust the directory is pretty bad.
GitSpawn: A Single Flaw Let's Untrusted Repos Run Code in Claude Code, Codex, Cursor, and Grok
[flagged]