4 ms·
unconstrained AI agents are what makes it so useful though. I have been using claude for almost a year now and the biggest unlock was to stop being a worrywart
by vardalab 7mo ago
unconstrained AI agents are what makes it so useful though.
I have been using claude for almost a year now and the biggest unlock was to stop being a worrywart early on and just literally giving it ssh keys and telling it to fix something. ofc I have backups and do run it in VM but in that VM it helps me manage by infra and i have a decent size homelab that would be no fun but a chore without this assistant.
- kristofferR 7mo agoAgree, but SSH agents like 1Passwords are nice for that. You simply tell it to install that Docker image on your NAS like normal, but when it needs to login to SSH it prompts for fingerprint. The agent never gets access to your SSH key.
- sersi 7mo agoI run my AI agent unconstrained in a VM without access to my local network so it can futz with the system however it wants (so far, I've had to rebuild the VM twice from Claude borking it). That works great for software development. For devops work, etc (like your use case), I much prefer talking to it and letting it guide me into fixing the issue. Mostly because after that I really understand what the issue was and can fix it myself in the future.
- bigstrat2003 7mo ago> unconstrained AI agents are what makes it so useful though Not remotely worth it.
- hrmtst93837 7mo ago[flagged]
- throwingSE 6mo agojai is doing the right thing for its threat model. The credential layer is a different surface though ... an agent with a broad API token can call initiate_payment or update_vendor_bank on a remote production system and the filesystem sandbox can't help. Applying the same principle as jai for remote boundaries, we can scope API authority to the task