Tilde.run – Agent Sandbox with a Transactional, Versioned Filesystem
Roll back any agent run like a Git commit with a single command.
A persistent, searchable filesystem for AI agents.
MCP integration lets Claude Code use this as long-term agent memory.
AI agent developers, multi-agent system builders
LangChain memory · LlamaIndex stores · Agent memory tools
If you saw my last post, we've been building agent-swarm (https://github.com/desplega-ai/agent-swarm) for a while, and one of the problems that we started encountering and getting more annoying each time was: how do we share / check stuff bi-directionaly with the agents (they run remotely).
Use case ---
The use case is simple: agents create a document somewhere and I want to be able to check it, leave comments, etc. But also for the other agents (in other machines / dockers) to be able to check it.
Until now the solution was simple: docker volumes. We mounted a /workspace/personal (personal volume) for each agent, and a /workspace/shared (shared volume in lead and workers). This allowed easy collab in the swarm, but not easy for me. I had to either SSH or have the swarm build an app and serve it locally via proxy :D.
Problem ---
On the other hand last week I decided to figure out other places to deploy this, and I tried fly.io, which I liked the DevEx a lot. The problem with it was that each machine allowed a single volume. I then tried Archil (which worked, but it was a ownership and setup mess).
Solution ---
So... ended up creating agent-fs, which is an s3 backed suuuper simple API (comes with MCP and CLI) that let you have an interface like the one from GDrive, but thought for agents.
When I published the npm I asked the swarm to register, and in less than 5 minutes I was already seeing the shared drive and docs they created in the live UI.
Why not use gws cli? Because I want each agent to be able to auto-register with an email (we use agentmail for them), get an API key and get going. It should be headless. Invites should be easy and each register comes with an initial personal drive.
Also this allows something nice (and silly). If you register as a human and have a shared drive w the swarm. Using the MCP insta allows to have that in any place with MCP support (e.g. Claude web, ChatGPT) which is a fast way to have a knowledge base across systems.
Thoughts on this?
Roll back any agent run like a Git commit with a single command.
MCP-compatible workspace where agents and humans edit the same versioned files.
Finally, Vercel for agents — filesystem access without stitching infrastructure together.
Hosted memory when Claude Code and Manus already do this locally for free.
CRDT-based VCS for AI swarms where Git's locking model fails completely.
Three-method API for agent memory, but semantic memory systems aren't novel anymore.