Another AI fail. Letting AI write code and modify your file system without sandboxing and buckups. What could go wrong?

  • Melody Fwygon@beehaw.org
    link
    fedilink
    arrow-up
    4
    ·
    1 day ago
    With the Obvious exclusions being mentioned here, where you should see them first...
    • IGNORANCE, regardless of if it was willful or blissful unawareness of the dangers
    • AI researchers…and other research interests
    • Science involving intelligence
    • Other Computer Science tinkering and experimenting…

    I can’t imagine why anyone would allow an AI to interact with files that have not been thoroughly backed up and secured on a disk that is detached from any system the AI is running on.

    Secondly, I cannot imagine why one would ever permit the AI to use move commands when getting files from a directory that is external to the directory you explicitly designate as the AI’s workspace.

    Third, why would someone not make sure all the files are in the right places yourself? It takes maybe 5 minutes tops to crack open a file explorer window and do the file operations exactly as you intended them; that way it’s ensured that a ‘copy’ operation and not a ‘move’ operation is used on the files, while doing any versioning, backing up or checkpointing that is desired.

    Last of all; why would someone use an LLM to make simple commands to a machine that they could easily do in one CLI command or one GUI interaction? If one can type an entire sentence in natural language to an AI, and they are skilled enough to set up and use that AI agent as a tool, why not simply type the command they intended, or do the GUI interaction necessary to do the task?