project
GitHub agent feature reported to have read private repository contents and posted them as a public comment.
No evidence-backed relationships are recorded.
A GitHub and Yale survey of 1,039 opted-in users puts interest in energy-efficiency tooling at 80% and interest in measuring impact at 74%, while the same post says runtime alone does not prove that energy use or emissions fell.
Reality
GitGuardian argues that credentials and permissions decide how bad an agent incident gets. Checked against the three 2026 disclosures it cites, the argument holds up, and only one of the three involved steering a model.
Reality
Running several coding agents on one machine is a concurrency-control problem. The boundary a git worktree draws stops well short of the ports, caches, credentials and merge queue where the collisions actually happen.
Reality
Agentic Workflows will start a coding agent inside a microVM with its own Docker daemon, so root-level freedom stops meaning root on the CI runner.
Reality
A hostile Git repository was enough to run code on a developer's machine, and three more agent failures landed the same month. The blast radius is whatever the developer can reach.
Reality