Show HN: Tilde.run – Agent sandbox with a transactional, versioned filesystem

I had to dig hard to find this is a SAAS sandbox offering not an actual sandbox (the software i can use locally). Its just wasting peoples time, no one needs a non opensource sandbox. There are now at least 3 apache 2 projects (smolmachines, microsandbox, boxlite) working on sandboxes and at least one of them should be ready for primetime soon.

Git is already versioned, S3 support versioning and any file copied into the sandbox, is well a copy, so I am not sure what is the angle here.Other than that it looks cool!

Nice work on the website!Building something for the same problem but more so from the perspective of self-hostable stateful sandboxes, and not just the filesystem (see https://bhatti.sh). What sandbox solution are you using here?

I made something pretty similar to this a couple months ago, when I was just getting into using coding agents. Has 2 parts that work individually but are better together: a change tracking FS and an agent sandbox. Haven't really used it though as it's a pain to get Claude Code working in that - Docker-based - sandbox without baking it in, and I really want something that's fully configurable. And then I didn't really need it to because I'm a very interactive user; I'm almost constantly watching the agent and never use YOLO... except for 1 codebase where it's frustratingly failing to fix a single particular bug and I really don't want to deal with it myself.

This is an excellent idea who's time has come.But this is too vague for me. I'm not seeing my questions answered in the landing page or FAQ either.E.g.,... what's the pricing?How does atomic commit really work? E.g., if one write to S3 succeeds but the update to a git repo fails?Does this use optimistic locking or something else? What happens if I commit changes to a resource that was updated since it was imported?Where/how is it hosted?

Back in the 1970's when versioned filesystems were invented, they provided a recovery path for when a file was improperly changed or deleted. Now, in the age of LLMs that go rouge, I can see why they would become popular again.

Does this provide gitflow to handle conflicts from multiple agents touching the same file system or is it purely for single-branch sequential iterations on the filesystem?I have a use case that could use this if it supports handling branching and merging file systems.

It was a nice surprise seeing your post on the first page of HN Oz, congrats!If I understand correctly what Tilde is doing is extending the concept of the sandbox in an operating system - filesystem, to data too.So this is a sandbox environment someone would use for data heavy agentic workloads, is this correct?

I was trying to build an agent. None of the sandboxes out there had solved the filesystem problem. I want my agent to have a persistent storage, and that stays forever. Like a human with a computer. When the agent spins up again, it has access to the computer with the same files.I had to create my own setup using aws s3 filesystem and docker for this.Does Tilde solve for this?

Just my two cents: less is more and the first impression matters a lot. I'm saying this because we see a new agent sandbox tool on the front-page almost every day. Most of them have an AI-made landing page design, lots of animations, lots of words. This has become a bad sign for me. I can tell that you put time into it, made a video, and everything, but I guess I'm suffering from some kind of fatigue of having to go through all these tools. So, the less I have to process to get to the meat of exactly what I'm looking at, what sets this apart from others, why and when I would need to use it, then the more likely I am to actually engage with the product.