top | item 47099359

(no title)

nnevatie | 8 days ago

That's it basically. I do not think running the tool in a container really solves the fundamental danger these tools pose to your personal data.

discuss

order

zozbot234|8 days ago

You could run them in a container and put access to highly sensitive personal data behind a "function" that requires a human-in-the-loop for every subsequent interaction. E.g. the access might happen in a "subagent" whose context gets wiped out afterwards, except for a sanitized response that the human can verify.

There might be similar safeguards for posting to external services, which might require direct confirmation or be performed by fresh subagents with sanitized, human-checked prompts and contexts.

brap|8 days ago

So you give it approval to the secret once, how can you be sure it wasn’t sent someplace else / persisted somehow for future sessions?

Say you gave it access to Gmail for the sole purpose of emailing your mom. Are you sure the email it sent didn’t contain a hidden pixel from totally-harmless-site.com/your-token-here.gif?