Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

news.ycombinator.com

Post reply on HN
Print view View original

51–60 of 95 posts

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

#51

Post by hamasho »

Hmm.. so this is not the same category with computer use or browser use. I love the idea. Well defined and controlled sandbox is really useful. Off topic but I’m disappointed by computer use and browser use when I tried three months ago. They couldn’t complete many basic tasks. Especially browser use, it easily failed slightly unorthodox website. It can’t find select box implemented by div, stacks in infinite loop when the submit button is disabled, and it even failed to complete the demo in its own readme! I’m okay with open source projects a bit buggy, but a VC funded company, which already has the fancy landing page, provides the service to big corps, and offers paid plans, should at least make sure the demo works.

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

#52

Post by verdverm »

devonkelley wrote: post #30
verdverm wrote: 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

[dead]

Given what OP describes

> Our biggest pain point with hosting agents was that you'd need to stitch together multiple pieces: packaging your agent, running it in a sandbox, streaming messages back to users, persisting state across turns, and managing getting files to and from the agent workspace.

The k8s ecosystem already handles most this and your agent framework the agent specifics. What you are talking about is valid, though a different axis imo. Quality and guardrails are important, but not discussed by OP.

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

#54

Post by vivekraja »

nr378 wrote: post #38

Based on the docs and API surface, I think the filesystem abstraction is probably copy-on-mount backed by object storage. I suspect it works as follows: when a task starts, filesystem contents sync down from S3/R2/GCS to a local directory, which gets bind-mounted into the container. The agent reads and writes normally - no FUSE, no network round-trips per file op. On task completion or explicit sync, changes flush ba…

That's a good analysis:) We want to go with FUSE but the performance overhead, especially with multiple calls to use files, is a constraint

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

#55

Post by vivekraja »

p0seidon wrote: post #53

When building, did you not have the thought or feeling that you would prefer the actual Claude Code and Codex harness to run, rather than just the SDKs also for your Agents?

You can use the default Claude Code harness with Claude Agent SDK (just set the prompt preset to claude code). Same with Codex.

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

#56

Post by shykes »

vivekraja wrote: post #27
adi4213 wrote: post #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 Cla…

We don't support docker-in-docker yet, but that's something on our short term roadmap. We have the need for this ourselves! For now, you could call a different service to spin up your sandbox with the image of your codebase. Not ideal, but this is what we do now. Yes, you can use your own subscriptions as long as you follow their guidelines

Dagger (dagger.io) has its own container execution stack, and supports dagger-in-dagger natively, with logical scoping, and without depth limit. Would love to show you both a demo, if you're interested!

(Disclaimer, I'm the CEO of Dagger)

I founded Docker, and lack of proper nesting support was always a pet pieve of mine. I couldn't fix it in Docker, so I fixed it in Dagger instead :)

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

#57

Post by verdverm »

jwoq9118 wrote: post #48
verdverm wrote: post #4

Earlier quoted context omitted.

Glad to find comradery! I've started the CLI interface to my custom agent since lol The reasons are (1) it's faster to do admin work like naming or deleting old sessions (2) I have not gotten the remote setup to work yet (haven't tried) but I do want to use it somewhere But yeah, it's gotten worse, the latest I recall is a new diff viewer for AI in the terminal (I already have git and lazygit)

It's hilarious to me how we are recreating decades of IDE advancements such that they work on the terminal, only for us to end up with what is essentially an IDE.

I was doing that with (neo)vim and reached the point that I wanted to stop having to maintain a sorta-IDE. I'm now doing the same with agents (custom vscode extension), but I find this different for a number of reasons, primarily that I don't want Big Ai deciding how I can interact with and use Ai.

One thing I took from ATProto is a strong belief that user agency and choice are the penultimate design criteria. To those ends, I think that any agentic tooling needs to support the majority of users' choice about how to interact with it (SDK, API, CLI, TUI, IDE, and Web). My custom agent is headed that way anyhow, because there are times where I do want to reach for one of them, and it's easier to make it so with agents working on their own codebase (minus vscode because the testing/feedback I haven't figured out yet)

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

#58

Post by punkpeye »

jsunderland323 wrote: post #26
adi4213 wrote: post #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 Cla…

Hey I'm working on this problem (also a YC company but it's FOSS). It's a Dind approach https://coasts.dev/ , I wonder if this works for your setup.

Cool project!

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

#60

Post by jsunderland323 »

punkpeye wrote: post #58
jsunderland323 wrote: post #26

Earlier quoted context omitted.

Hey I'm working on this problem (also a YC company but it's FOSS). It's a Dind approach https://coasts.dev/ , I wonder if this works for your setup.

Cool project!

Thanks! Still ironing out early kinks but I have a couple of friends using it. It’s been a joy to work on.
Post reply on HN