Can you explain why everyone thinks we should use new tools to deploy agents instead of our existing infra? eg. I already run Kubernetes
Launch HN: Terminal Use (YC W26) – Vercel for filesystem-based agents
11–20 of 95 posts
Re: Launch HN: Terminal Use (YC W26) – Vercel for filesystem-based agents
#12Can you explain why everyone thinks we should use new tools to deploy agents instead of our existing infra? eg. I already run Kubernetes
Agents run on infra, they have network connectivity, they have ACLs and permissions that let them read+write+execute on resources, they can interact with other agents.
To manage them from both an infra and security perspective, we can use the existing underlying primitives, but it's also useful to build abstractions around them for management, kind of like how microservices encapsulate compute+storage+network together.
I think of agents as basically microservices that can act in non-deterministic ways, and the potential "blast radius" of their actions is very wide. So you need to be able to map what an agent can do, and it's much easier to do that if there are abstractions or automatic groupings instead of doing this all ourselves.
Re: Launch HN: Terminal Use (YC W26) – Vercel for filesystem-based agents
#13have you guys found any of the existing nfs tools helpful (archil, daytona volumes, ...) or did you have to roll your own? i guess i have the same question for checkpointing/retrying too. it feels like the market of tools is very up in the air right now.
1. we're not NFS, we wrote our own protocol to get much better performance
2. we're planning on coming out with native branching this month, which should make these kinds of workloads much easier to build!
Re: Launch HN: Terminal Use (YC W26) – Vercel for filesystem-based agents
#14Re: Launch HN: Terminal Use (YC W26) – Vercel for filesystem-based agents
#15Can you explain why everyone thinks we should use new tools to deploy agents instead of our existing infra? eg. I already run Kubernetes
I think Kata containers with Kubernetes is an even better sandboxing option for these agents to run remotely.
Shameless plugin here but we at Adaptive [1] do something similar.
Re: Launch HN: Terminal Use (YC W26) – Vercel for filesystem-based agents
#161) Can I use this with my ChatGPT pro or Claude max subscription? 2)
Re: Launch HN: Terminal Use (YC W26) – Vercel for filesystem-based agents
#17Can you explain why everyone thinks we should use new tools to deploy agents instead of our existing infra? eg. I already run Kubernetes
I think Kubernetes is a good candidate to run these sandboxes. It is just that you have to do a lot of annotations, node group management, pod security policies, etc., to name a few. Apply the principle of least privilege for access to mitigate risk. I think Kata containers with Kubernetes is an even better sandboxing option for these agents to run remotely. Shameless plugin here but we at Adaptive [1] do something s…
The permissions issues you mention are handled by SA/WIF and the ADK framework.
Same question to OP, why do you think I need a special tool for this?
Re: Launch HN: Terminal Use (YC W26) – Vercel for filesystem-based agents
#18Re: Launch HN: Terminal Use (YC W26) – Vercel for filesystem-based agents
#19Can you explain why everyone thinks we should use new tools to deploy agents instead of our existing infra? eg. I already run Kubernetes
I think there are some primitives for agents that need to be built out for better security and being able to reason about them. Agents run on infra, they have network connectivity, they have ACLs and permissions that let them read+write+execute on resources, they can interact with other agents. To manage them from both an infra and security perspective, we can use the existing underlying primitives, but it's also use…
tl;dr, I don't think the shovel analogy holds up for most of the Ai submissions and products we see here.