Viewing profile — dangtony98

Yeah this should work in an interface agnostic way so be it that the agent invokes CLI, MCP, SDK, or makes an API call, all traffic is routed through the proxy. That said, there ar…

The sandboxed agent and AV should ideally not run on the same host because if it did then you're right that a sufficiently sophisticated agent like Mythos could try to reverse engi…

This would be deployed separately but in close proximity to your sandboxes. You'd want to add network restrictions around sandboxes to only allow outbound requests to AV. You'd add…

What attack vector are you thinking? Could you elaborate more. Would love to explore this train of thought and what we can do about it.

Yup! I think the terminologies we're going to be seeing more and more of are "credential exfiltration" and conversely "credential brokering" as a solution to that.

Not yet for both but this would definitely be on the roadmap; especially the credential stripping portion. For AV to be really useful, it'd have to support more protocols but we th…

Thanks for this feedback! Will keep in mind all of these points as we iterate on Agent Vault. We're pretty swarmed on requests at the moment but I've noted these down as improvemen…

Hey! Yeah I think there's overlapping functionality for sure, and you're spot on on people looking at it from different angles. The "connectors angle" is something we thought about…

Yup it turns out many teams building their own custom agents end up stitching together their own solutions for this problem. What we thought was basically: If everyone is making so…

[dead]

Agent Vault should remain in close proximity to the sandboxed agent and not be exposed to the public internet; your standard network security controls apply. The proxy itself curre…

We're still in the early innings of credential brokering so there'll be a lot of overlap but I expect the way the tool evolves will start to diverge a lot since we are thinking ver…

Can you please elaborate on the agent signing up for a service piece? I'm curious to understand the use case more (type of agent, what credit, etc.). The current modal assumes that…

I haven't used executor.sh but this seems to operate at a different layer from Agent Vault. From what I'm seeing, executor.sh is an integration and execution layer for agents. Wher…

I'm so glad you mentioned the non-cooperate sandbox! Did you get a chance to try it out? This is something that we're going to be improving significantly in the next week including…

To be honest, I haven't used OneCLI personally before so I can't speak to it in detail but Agent Vault does take a similar approach with the MITM architecture and setting HTTPS_PRO…

Hey! At the moment Agent Vault doesn't address the identity piece. The identity piece would be the next logical step at some point likely after we figure out the optimal ergonomics…

Thank you! Me too - very excited to see where this goes :)

T from Infisical here - Also forgot to mention that this is a research preview launch for Agent Vault and should be treated as such - experimental Since the project is in active de…

We'll be releasing a closer integration between Agent Vault and Infisical in the coming 1-2 weeks! The way we see it is that you'd still need to centrally store/manage secrets from…

It prevents a compromised agent from seeing the secret. There are two different but related problems here: credential exfiltration and data exfiltration. The problem that Agent Vau…

Yeah so Agent Vault (AV) solves the credential exfiltration problem which is related to but different from data exfiltration. You're right that if an attacker can access the proxy …

Hey HN! Today we're launching Agent Vault - an open source HTTP credential proxy and vault for AI agents. Repo is at https://github.com/Infisical/agent-vault , and there's an in-de…