Llm

A coding agent in VS Code got "No route to host" for every host on the subnet except the router, and blamed the Wi-Fi. macOS was blocking VS Code, which lacked the Local Network permission that Terminal gets automatically.

Every ansible-playbook run from a coding agent failed before reading the playbook, even --syntax-check. The agent shell hands Ansible non-blocking file handles; `&1 | cat` gives it blocking ones.

Security transcripts mix observations with model guesses, and classifiers may stop the audit. Preserve provenance, checkpoints, and a provider-neutral handoff.

A model may leak encoded prompt fragments yet corrupt the final decode. Capture verbatim tokens, preserve case and order, and transform them deterministically.

Three times a coding agent read a result from a check that never ran: zsh's `log` builtin (`(eval):log:1: too many arguments`) hid `/usr/bin/log`, `cargo test --exact` matched no test and passed, and an empty variable from "argument list too long" made 400 of 400 runs fail.

A branch built with a coding agent passed lint, 1,572 Python tests and 418 GUI tests. A review by a different model, split into a Standards subagent and a Spec subagent, still found two ways to write the same record twice. The Spec reviewer got there by checking what the commit messages promised against the code.

A coding agent found a bug mid-refactor and parked it as a known issue with `@unittest.expectedFailure`. Two `git log -S` runs showed nobody had ever decided it, so it was fixed the same night. The obvious `.extend()` fix would have broken an alias. Includes the skill that does the dating.

An upload classifier sent a language model the first page of each PDF. The helper indexed a dataclass like a list, the TypeError was caught and turned into an empty string, and for seven weeks the model classified every PDF by filename alone, with a confidence score attached.

Inside its sandbox, a coding agent hit "Could not find a working container runtime strategy" and "listen EPERM: operation not permitted 0.0.0.0:8080", filed every failure under "environment" and committed. On the host, three tests failed, and the skipped `next build` stayed broken for two months.

A coding agent ran pnpm test and got ERR_PNPM_ABORTED_REMOVE_MODULES_DIR_NO_TTY from pnpm 11, in a repo pinned to pnpm 10. The agent's runtime ships its own pnpm and turns off the packageManager check. Following the CI=true hint reinstalled node_modules, filled the disk, edited pnpm-workspace.yaml and lost a native Next.js binary.