How would Emu enforce a denial when the other agent runs in the cloud?
We are building https://stashbase.dev for coding agents, and that’s been the tricky part: a rule needs a place where access can actually be blocked. With local processes you can restrict filesystem and network access; with external services you need control over the credentials or even request path.
Also I think that most "hard" agent permissions and rules should be enforce outside of the model because if the agent is "self-learning" there's a chance it can learn to do something that should not be done. This is a direction we are taking, permission profiles and access that wrap the agents.
We are building https://stashbase.dev for coding agents, and that’s been the tricky part: a rule needs a place where access can actually be blocked. With local processes you can restrict filesystem and network access; with external services you need control over the credentials or even request path.
Also I think that most "hard" agent permissions and rules should be enforce outside of the model because if the agent is "self-learning" there's a chance it can learn to do something that should not be done. This is a direction we are taking, permission profiles and access that wrap the agents.