Hacker News Reader

Comment by SamInTheShell | Hacker News Reader

The problem is trivial to solve. Treat AIs like they are users. We have user space for a reason. We have linux namespaces for a reason. We have real airgap architectures where the data center can't even connect out.

When you're a company running around with more than a few billion in the vault, you have no excuse for the level security negligence going on at every phase of rollout.

I gawked at Cursor executing a python script one time and decided enough was enough, I don't raw dog these tools anymore because their developers are the dumbest people to task with security work. They just don't care.

View on HN

So how would you go about sandboxing Muse in a way that it still functions as a general purpose assistant?

> that it still functions as a general purpose assistant

What features you want it to have? The thing you're saying is super vague, I would just say that one belongs in cloud.

If it must run things on the user's machine, it's gotta be in a rootless container and not be root inside the container. All tools belong in the container. Folder access explicitly configured by the user.

Like I already did this for my local AI: https://github.com/SamInTheShell/loom

It's not perfect or even done, but it works and it shows the security model that should be standard for aligned models we're running.

Unaligned models, absolutely different story.

Also VM is better than container for security, but containers are a bare minimum for me.

Let's say I have an aligned agent, and I want to give it access to my bank account to track my budget, and my email so it can automate responses to certain messages, and automatically unsubscribe from junk emails.

Nether service has a way to configure fine-grained access for a secondary user.

How do I go about giving the agent the ability to perform these tasks without exposing myself to the risk of unexpected destructive behavior from the agent?

Those are API things. Should be an API, build an MCP server for it. Doesn't touch the PC. About the automated responses, that's a write operation, therefore requires user consent.

If you want to design a system specifically to make sure you're not going to get stonewalled for sending me an emdash, you build and maintain a set of permissive rules for sending/reading to avoid my blacklist of people I'll never work with.

Once you got API stuff sorted, just throw a cronjob at it or build a service for that stuff.

^ There be prompts all over the place here, obviously. Realistically your MCP server will end up hacking on POP3.

Reply on news.ycombinator.com