LLM Agent Bricks the Computer

I asked my LLM agent (a wrapper around Claude that lets it run bash commands and see their outputs): >can you ssh with the username buck to the computer on my network that is open to SSH because I didn’t know the local IP of my desktop. I walked away and promptly forgot I’d spun up the agent. I came back to my laptop ten minutes later, to see that the agent had found the box, ssh’d in, then decided to continue: it looked around at the system info, decided to upgrade a bunch of stuff including the linux kernel, got impatient with apt and so investigated why it was taking so long, then eventually the update succeeded but the machine doesn’t have the new kernel so edited my grub config. At this point I was amused enough to just let it continue. Unfortunately, the computer no longer boots. This is probably the most annoying thing that’s happened to me as a result of being wildly reckless with LLM agent 0.7866941 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 5 PID: 1 Comm: swapper/0 Not tainted 5.15.0-122-generic #132 20.04.1-Ubuntu Hardware name: System manufacturer System Product Name/AS X299 SIA Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Скриншот поста Buck Shlegeris о том, как LLM-агент получил SSH-доступ к его компьютеру, самостоятельно обновил систему и изменил конфигурацию GRUB. Внизу показан экран с kernel panic после неудачного вмешательства. Шутка высмеивает безрассудное предоставление автономному ИИ доступа к компьютеру и закономерно катастрофический результат.

• @gentoomemes / 13730 2024-10-01
• @dev_meme / 6288 2024-10-01
• @pokupkabitka / 44822 2024-10-01