Development record
2026-10-16 — The product thinker changed the brief for iss-2610161612200864 from teaching alone to teaching and enforcement: the guard refuses a bash -c or sh -c script built from variables that runs rm, rmdir, unlink or shred, and the refusal says how to rewrite it (write the script to a file in one command and run it in the next; delete with literal paths through /bin/rm -f --, or a variable guarded as "${VAR:?}", outside the -c string), rather than warning. The agent gets the reason back and rewrites the command before the host would stop to ask a person. Only that shape is refused: a -c script with no deleting command, or one with no variable in it, still passes.
2026-10-16 — The product thinker changed the brief for iss-2610161612200864 from teaching alone to teaching and enforcement: the guard refuses a bash -c or sh -c script built from variables that runs rm, rmdir, unlink or shred, and the refusal says how to rewrite it (write the script to a file in one command and run it in the next; delete with literal paths through /bin/rm -f --, or a variable guarded as "${VAR:?}", outside the -c string), rather than warning. The agent gets the reason back and rewrites the command before the host would stop to ask a person. Only that shape is refused: a -c script with no deleting command, or one with no variable in it, still passes.
Frontmatter
| id | dcn-2610161621028613 |
|---|---|
| type | decision |
| date | 2026-10-16 |
.abcd/work/decisions/dcn-2610161621028613-the-product-thinker-changed-the-brief.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610161612200864Agents stall at the host's permission prompt when they write a command the host cannot check. On 2026-10-16 a background agent ran a bash -c script built from variables that deleted files. The host could not check it, so it asked 'This shell -c script runs rm and could not be checked. Do you want to proceed?', and the agent waited for a person. No bundled rule teaches the forms the host can check.