It shouldn't.
replyBe as close as AGI we are (/s), this issue from 2018 is still open:
https://github.com/microsoft/vscode/issues/52116
I don't know what we are doing.
Probably a good idea to only run LLMs with a dedicated user account, or in a container.
replyDedicated user account does not work as eventually all your code and data will move under that.
replyI run it in an ephemeral container sandbox (https://github.com/ashishb/amazing-sandbox) which has access to the current working directory and it drastically limits the attack radius.
If all the code and data eventually move into the dedicated user account, why wouldn't it also eventually move into the container/vm?
replyDon't mount all your code every time.
replyE.g. when working on a frontend only project, you don't need to mount the backend directory and vice-versa. This limits the attack radius.
I’m fine with that. I use a top-level directory for all of my code, and restricting extension access to that directory is a great idea.
replyIt is good but you still don't want long running background tasks.
replyWhen you run a linter, for example, then it should stop executing cider once it stops. And not be able to spawn long-running background tasks for infiltration.
That looks really nice, including the VSCode/Mac wrapper.
replyFor locally installed Code / Code-fork extensions, there is not any concept of permissions (at least on Windows or MacOS (+ the 3rd party code-server running on Linux)), correct?
replyDoes it? It asks for permission to use whatever directory you call it in.
reply