03 · Editor’s Letter
They clicked don’t ask again. The password stayed in the saved command.
Yesterday the letters were about a quiet refusal. Today they are about a loud approval that does not know when to stop.
ByteByteGo walks the Claude Code request loop end to end: prompt, interface wrapping context, agent loop, permission system, tool call, execution, result, state. The permission step is not decoration. Joe Njenga’s Medium preview says Claude Code asks before shell commands, and on the third ask people click “Yes, and don’t ask again.” What gets saved, he writes, is that exact command string, including any database password. He claims 2,539 secrets exposed. We have only the preview, so the methodology stays his.
The same Sunday bag holds the other side-effects. Mark Craddock’s ArcKit preview splits reading a bid from scoring it so a supplier bid cannot reach the scorer. Roan Brasil Monteiro says a 2.5-point eval drop after a harness swap can be noise before anyone rolls back. Elvis Saravia’s AI Agents Weekly puts GPT-6 Cyber at Critical under the Preparedness Framework, with ExploitGym at 48.5 percent against 32.1 percent for GPT-5.6 Cyber. Tom Krazit’s Runtime letter watches Honeycomb ship Personal and Team Agents for SREs drowning in agent code, with Brendan Burns calling much of that code eventually “transient.”
The claim is one line. Permission fatigue is not a UX quirk. It is how secrets, scores, evals, and exploits leak into the saved state.
Skip cover