Live data from Hacker News

Launch HN: Terminal Use (YC W26) – Vercel for filesystem-based agents

news.ycombinator.com

11–20 of 95 posts

Re: Launch HN: Terminal Use (YC W26) – Vercel for filesystem-based agents

#11
post #2

Can you explain why everyone thinks we should use new tools to deploy agents instead of our existing infra? eg. I already run Kubernetes

At least on K8s you can control the network policy. That's the harder problem to solve. I suspect we'll see a lot of exfiltration via prompt injection in the next few years.

Re: Launch HN: Terminal Use (YC W26) – Vercel for filesystem-based agents

#12
post #2

Can 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 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

#13

have 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.

howdy! two things on the archil front:

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

#15
post #2

Can 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 similar.

[1] https://adaptive.live

Re: Launch HN: Terminal Use (YC W26) – Vercel for filesystem-based agents

#16
This is really interesting, congrats on the launch. The use case I’m trying to solve for is building a coding agent platform that reliably sets up our development stack well. Few questions! In my case, I’m trying to build a one-shot coding agent platform that nicely spins up a docker-in-docker Supabase environment, runs a NextJS app, and durably listens to CI and iterates.

1) 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

#17
post #2

Can 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…

We already do those things with k8s, so it's not an issue

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

#19
post #2

Can 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…

Right, those abstractions and controls already exist in the Kubernetes ecosystem. I can use one set of abstractions for everything, as opposed to having something separate for agents. They are not that different, the tooling I have covers it. There are also CRDs and operators to extend for a more DSL like experience.

tl;dr, I don't think the shovel analogy holds up for most of the Ai submissions and products we see here.

Post reply on HN