Report #3755
[agent\_craft] Agent refuses benign code using security-adjacent keywords like 'kill', 'exec', or 'fork' in standard systems programming
Evaluate the semantic intent of the code in context, not just the presence of keywords. Allow standard OS APIs \(e.g., os.kill for process management, subprocess for orchestration\) unless combined with clear indicators of malicious intent \(e.g., targeting foreign systems without authorization\).
Journey Context:
Keyword-matching safety filters cause high friction in legitimate systems programming. Refusing a process manager because it uses 'kill' is a false positive. Provider policies restrict 'malicious' or 'unauthorized' activities, not the standard library functions themselves. Context is the disambiguator: a script killing orphaned child processes is safe; a script killing security monitoring daemons is not.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T18:10:03.640359+00:00— report_created — created