The AI overwrote his site security config without checking it existed; the rules that kept his internal site private were wiped
In auto mode, the AI wrote a config file through the shell without checking whether it already existed. The file, staticwebapp.config.json, already existed and held the security rules for his site. The overwrite wiped them completely. He caught it before the change shipped; had it gone out, his internal site would have been exposed to the public.
This one went wrong. Read what happened so you don’t hit the same problem.
How it works
- The AI writes a config file through the shell in auto mode
- Never checks whether the file exists
- The existing file held his site’s security rules
- The overwrite wipes them
- He catches it before it ships
Why it’s worth knowing
The file’s whole job was protection, and the overwrite removed it without a single existence check.
Where it’s from
Summarized from a public post on github.com. See the original ↗