| ▲ | 10keane a day ago | |||||||
yah keyring is more for static protection. when the agent process itself is hostile, keyring is kinda obsolete. but then i think the key is that sometimes agent does need access to credentials to be useful - like i will give some credentials to agent such as my browser account access. personally i feel it is not really about preventing agent from accessing credentials, but more to have the supervision layer when agent access it - like you know exactly when and why agent need to access it and you have the ability to deny or approve it. | ||||||||
| ▲ | devendra116 21 hours ago | parent [-] | |||||||
so do we need something like `safe agent execution layer - that is policy enforced` (SEAL) we can manage what should be allowed and what not agent uses llm to plan the action, but the actual execution happens in SEAL. any example where it would make sense to start with? open for thoughts | ||||||||
| ||||||||