@RhysSullivan But computer use for oauth credentials generation feels like a hack which can break anytime. Most of the flows need human intervention which is a deliberate design decision.
@RhysSullivan - Couple of mac minis added as deployment options in codex and cursor as background agents
- All source controlled with a shared-mcp-servers repo
- Have global config file per machine that contains the tokens with correct access control.
@_nishankj Sounds good, but if there are issues in the intermediate steps in the script running in V8, the model might fall back to the same individual tool call tendencies.
Definitely saves tokens for straightforward queries.
@audiencon Sesame lets you approve exactly what your AI agent can do — which endpoint, which method, what scope, for how long — and revoke that access in one click. https://t.co/XRRseXReW0
@hthieblot Sesame lets you approve exactly what your AI agent can do — which endpoint, which method, what scope, for how long — and revoke that access in one click. https://t.co/2FGauWsdAz
Stop pasting API keys into agent prompts or memory files.
Your AI agent needs secrets. It doesn't need to see them.
Your agent tries to refund a customer. Sesame denies it. Only read access was authorized.
Brokered. Audited. Revoked in one click.
70+ providers, bring your own vault.