I dont this is top most priority. We do this with codex or claude in chrome and validate the UX.
I think BDD is going to be back in style for agent generate code.
When you generate at scale discovering, maintaining and scaling test is the major problem, thats why were katana [1] a behavior driven testinf utility thay discovers behavior and maintain, generates test cases.
See CC6.2 Creation and Removal of User Credentials and CC6.6 External Protections, but if you don't work in a regulated environment, world's your oyster!
Oh cool, feel free to reach out to me at andrew@workweave.ai if you ever want to share notes! We've learned a lot in the process of building this so far :)
All the points that you are mentioning, you can technically do with tools too. We do that at adaptive [1]. We are building privileges access stuff for agents, and it works. The usecases you are mentioning can be done with tools via our platform.
By tools, do you mean skills? Or do I misunderstand you?
Thanks for sharing your solution. I clicked around and the information on your site is sparse. The postgresql page[0] doesn't really illustrate how your system works; just says that it does.
Regardless, there's a big difference between a proprietary way to inject skills and MCP, a standardized way to control access and deploy AI compatible logic.
Apologies about the sparse information. We’re preparing for a launch. Thought this would be a great place to make the comment. It is indeed a combination of tools and skills.
Your argument is fair but yea, we are seeing adoption because tools often map to users mental model of how they want to use the agent.
[1] https://doc.akka.io/libraries/akka-core/current/typed/actors...