Replies: 1 comment 3 replies
-
|
Interesting you should mention as this is a WIP in PR #840 Under the hood: For each tool execution from within the child process, the supervisor creates an isolation tool execution within a new sandbox, as as the two have IPC, the supervisor passes back stdout/err etc to the child. It covers the exact examples you provided, in fact I demo'ed using NPM as an example (note the schema has improved since then) |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying nono sandboxing for local AI agents. One conceptual misunderstanding I have is that a single profile is applied to the parent agent process and then inherited for all sub-processes spawned by the agent. I would rather prefer to define fine-grained profiles for each agent tool instead of giving the agent itself all these capabilities.
A few examples:
I understand that a custom agent with nono SDK could apply specific profiles when starting tools. However, I wonder if this can be done in a declarative way. Also if I then start such an agent with minimal capabilities, will it be able to fork a tool process with additional capabilities it didn't have?
There is a related idea in #336, but I think that one goes more into manual confirmations rather than declarative per-tool profile.
Beta Was this translation helpful? Give feedback.
All reactions