Well, you could whitelist the tool in sudoers.
This would let LLMs use it too.
Well, you could whitelist the tool in sudoers.
This would let LLMs use it too.
For me, it took a bit over six weeks of Claude running unattended perpetually.
Also gave Opus 4.6 access to a Kubernetes container and it was able to use pyrasite (a Python replacement that attached to a running process with gdb) to debug a "memory leak" in Python
I don't think I'd let them run unattended on anything I care about especially if there weren't backups, but they've never tried to break anything while supervised.
Usually it's significantly faster and more accurate to give the LLM/harness access to the thing to debug then to try to copy/paste back and forth.
> "On my machine, after about 21 days of uptime, the main SSD has written about 37 TB," wrote developer Rui Fan, a project management committee member of Apache Flink. "Process/file-level checks show Codex SQLite logs are the main continuous writer
https://www.theregister.com/ai-and-ml/2026/06/23/openai-code...