buildOne report1 publisher Gemini CLI's resolver reads past a yolo default in settings.json
Gemini CLI skips a yolo value in settings.json and never turns on the sandbox for it, a dev.to read of the source found. Anyone who wants YOLO every session needs a shell alias and an explicit --sandbox.
Reality
- Evidence62
- Adoption
- Not scored
- Hype gap0
- Incentives
- Not scored
- Confidence60
buildConfirmed2 publishers Sakana AI and UC Berkeley's MASS method reached a 69.9% win rate against its Qwen3.6-27B base model after two rounds of self-training. The same model ranks its own runs, and its evaluator sometimes passes flawed steps into the next training set.
Reality
- Evidence50
- Adoption
- Not scored
- Hype gap+25
- Incentives
- Not scored
- Confidence62
Manifold Security reported eight instances across seven command-line agents. The command runs as the user, outside the sandbox, with no approval prompt, and four were still firing when the researchers retested on September 1.
Reality
- Evidence72
- Adoption60
- Hype gap+15
- Incentives55
- Confidence70
buildOne report1 publisher A repo's core.fsmonitor setting turns an agent's routine git status into code execution
GitSpawn, as summarised in a dev.to write-up of Cloud Security Alliance findings, uses a Git performance setting to run attacker code when a coding agent inspects a project it just opened. Seven agents are named.
Reality
- Evidence32
- Adoption
- Not scored
- Hype gap+18
- Incentives28
- Confidence40
buildOne report1 publisher Opening an untrusted repo made seven coding agents run the program its Git config named
Manifold Security's GitSpawn findings cover eight issues across seven coding agents. The path runs through core.fsmonitor, where a background git status starts a helper the repository chose, outside the agent's sandbox and with no prompt.
Reality
- Evidence34
- Adoption
- Not scored
- Hype gap+10
- Incentives
- Not scored
- Confidence38
buildOne report1 publisher A wiki that accepted GET as an edit gave read-only agents 18,000 writes
The wiki's old software took a plain GET as an edit, so a harness that policed request types could not stop the writes. GitSpawn puts the same gap in the startup git calls of seven coding agents.
Reality
- Evidence42
- Adoption52
- Hype gap+30
- Incentives78
- Confidence45
buildOne report1 publisher Harness choice moved token use 83-fold with the model held constant
The spread traces to two numbers you can read off your own logs: the tokens a harness spends before any work starts, and how many turns it takes. Together they predicted total token use with an R-squared of 0.99.
Reality
- Evidence58
- Adoption34
- Hype gap+12
- Incentives42
- Confidence55
buildOne report1 publisher Seven harnesses took the transcript. None of them took the approvals.
A frozen Claude Code session moved cleanly into seven rival agent formats. The approval and audit machinery wrapped around it moved into none of them.
Reality
- Evidence58
- Adoption20
- Hype gap+12
- Incentives38
- Confidence55