64 comments

[ 6.0 ms ] story [ 82.9 ms ] thread
Interesting. Their versioned storage sandbox seems to be what really sets them apart
I know everyones trying to figure out how to make money in this grift economy, but if you're a rational person, you know that it's all a bunch of gambling and tailoring your scope to b2b and ignoring local & open source models and tools, you're more likely going to be part of that permanent undeclass they keep talking about in a self-fullfilling prophecy.
Interesting. Literally saw a tweet talking about exactly this last night.

Not sure how I feel about it using on your hosted service, while your home page is asking me for analytics data and only the cli and sdk are open source.

I do not get it. If the agent is not mutating state the change can be checked in. If it is mutating external state, version control won't save you.
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.
As someone who is building an AI tool in this category, can you give examples? :)

I've tried to focus more on end-user use-cases in my own product positioning, even though security is absolutely at the top of my list. This was hard to watch because it felt it demonstrated a security feature that is really secondary to the purpose of an agent.

What would be a spin in this AI category that would excite or surprise you?

Anthropic is probably looking at this trend and building something. When released will kill couple of startups.
Do git and branching fit into this at all?
This looks pretty useful. The versioned filesystem part is nice becuase that’s exactly where a lot of agent stuff gets messy fast.
Interesting project. I am building an IDE for my phone and browser (www.propelcode.app) and have evaluated a few container architectures and providers. It was quite painful to get a prototype working. I will try your platform and would be happy to give feedback.
any chance i can run local micro-VM such as boxlite with this?
What compute resources does the sandbox have? Memory/CPU/GPU?
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?

Isn't that like working on a codebase with an agent?
Agent Sandboxes is the official k8s solution for this.
Nice, I think that's pretty neat. Do you have an idea where to take this further? I.e. for the filesystem it's great but what if you need to touch external systems that keep their own state?
All these agent offering are missing a use case.

What I would use it for and why?

It reminds me of a blockchain - where it was a solution desperately looking for a problem. What problem does it solve?

more tools I will never use or need theres just an endless supply of new open source projects now I stopped paying attention

I increasingly feel the impact of landing on the frontpage of HN is not as pronounced as it used to be. The demographic shift of HN is also noted, it has a lot more "reddit" vibe than I remember.

Before all the vibecoding when I saw some project even if I thought it was dumb or didn't appeal to me, there was still a level of respect for it because at least someone put the effort in to write the code and at least attempt to understand what they were doing. The more they understood they more they learned about programming even if the project itself isn't super useful for others.

Now I see these things and its more likely than not that it was spit out by an agentic tool with little to no understanding of the code, and hardly learning or effort took place. Feels cheap and a waste of time. Why spend my time looking at something that someone made in a few hours so they could up their fake portfolio?

Its great to find real development out there but these types of posts eg "Show: random agentic tool gibberish" feel cheap and flaccid now. Nothing impressive

How does the scale? For example if I were to have hundreds or thousands of concurrent agents running with some parts of their data pulled out of shared state and other parts custom to that particular agent run and I wanted all of this to be preserved for future collective or individual agent use later, is this a reasonable primitive for that problem space? Or is this more for a situation what you have one or a small number of productivity assistance agents that need a sandbox but low data mutation throughput and low amount of concurrent access across different agents?
> Free to start

Before I invest my time into something like this I'll need to know what it'll end up costing in the end. Perhaps it's just that "private previews" aren't for me. Good luck!

Looks promising! I wanna try it!
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?

If an agent deletes something important (e.g. database), can you undo it? Does it automatically backup before making changes?
(comment deleted)
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.

I implemented something like this in ADK with Dagger, but it misses some important features b/c of BuildKit underneath. The OCI foundations make saving each step as a layer, diff, clone/fork, and time travel easy. The hard parts are security and resource limits.

Glad to see more takes in this space.

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.