4 ms·
Is that the harness' job? It seems to me the best place for sandboxing is at the OS level (i.e. running the harness inside a container with correct access conf
by skohan 20d ago
Is that the harness' job? It seems to me the best place for sandboxing is at the OS level (i.e. running the harness inside a container with correct access configured).
- adverbly 20d agoI would argue that it is the harness's job... Certainly for any harness which is targeting an end user. They don't sell cars without seat belts, and it is the car manufacturer who has to do it. Also, small nitpick but technically a container doesn't give full isolation compared to something like a VM.
- skohan 20d agoOk that's fair if it's targeting a non-technical audience. But I think this will eventually be a problem solved at the OS level in a more streamlined way. I.e. there will be fine-grained permissions you need to approve to give an agent access to the system.
- jbstack 20d agoYou want both. The harness and the sandbox do different things. The harness says "You have access to tool X, Y, and Z, but not A, B, C". The sandbox says "If you try to use X to access a forbidden resource, I'll prevent you from reaching it".