Tilde wraps every AI agent run in a transaction with atomic commit/rollback, composing GitHub, S3, and Google Drive as a single versioned POSIX filesystem with per-call network auditing.
Key Takeaways
Every sandbox run executes in an isolated container; on clean exit changes commit atomically, on failure nothing persists, no manual cleanup needed.
GitHub repos, S3 buckets, and Google Drive mount together as ~/sandbox with full version history and instant rollback via one command.
All outbound network calls are policy-checked before leaving the container; cloud metadata endpoints and unauthorized hosts are blocked by default with a full audit log.
Agent-first RBAC gives agents scoped permissions with a readable DSL supporting ALLOW, DENY, and APPROVE (human-in-the-loop) per path and action.
Built on lakeFS, the open-source data versioning layer, providing battle-tested scale for object-level versioning across billions of files.
Hacker News Comment Review
Commenters pressed hard on unanswered atomicity mechanics: how does a cross-system commit stay atomic when, for example, one S3 write succeeds but a paired GitHub update fails, and whether optimistic locking handles conflicts on stale imports.
Multi-agent branching and merging support is an open question; the product appears designed for single-branch sequential runs, limiting multi-agent parallel workloads without clarification from the team.
Pricing opacity and private-preview gating are recurring friction points; multiple commenters said they will not invest evaluation time without knowing eventual cost.
Notable Comments
@seamossfet: asks whether gitflow-style branching and merging across agents is supported, flagging a concrete multi-agent use case that depends on the answer.
@kay_o: asks whether SQL databases are in scope or only the filesystem layer, a gap not addressed in the source text.
