Hacker News: ozkatz

Basha256.sh – Pure Bash 3.2 implementation of sha256

ozkatz — Mon, 29 Jun 2026 22:37:48 +0000

Article URL: https://gist.github.com/ozkatz/dc7606ea68138b75999cbb1b271072a6

Comments URL: https://news.ycombinator.com/item?id=48726264

Points: 6

# Comments: 0

New comment by ozkatz in "Lore – Open source version control system designed for scalability"

ozkatz — Thu, 18 Jun 2026 02:31:14 +0000

Curious if you’ve had a chance to try lakeFS?

It was designed with large-scale environments in mind. I’m aware of several deployments managing hundreds of petabytes of data and billions of objects, which is why lakeFS does not use Git’s Merkle tree / directory tree approach.

Disclaimer: I’m one of the project’s co-creators.

New comment by ozkatz in "Show HN: Tilde.run – Agent sandbox with a transactional, versioned filesystem"

ozkatz — Thu, 07 May 2026 02:28:23 +0000

That’s the current RBAC implementation: agents by default can make no API calls. the only way for them to contact the outside world is through a forward proxy configured in the sandbox. that proxy only allows making requests to destinations explicitly allowed (host, path, method)

New comment by ozkatz in "Show HN: Tilde.run – Agent sandbox with a transactional, versioned filesystem"

ozkatz — Thu, 07 May 2026 01:20:40 +0000

Appreciate the honest feedback. I agree there's a lot to improve there.

New comment by ozkatz in "Show HN: Tilde.run – Agent sandbox with a transactional, versioned filesystem"

ozkatz — Thu, 07 May 2026 01:18:14 +0000

very very fast: proportional to the count of objects modified, but not their size. Every commit represents a snapshot - an immutable listing of objects that represents the repository. reverting is essentially applying the inverse of the diff introduced by the reverted commit.

This is metadata only as the objects themselves are immutable.

New comment by ozkatz in "Show HN: Tilde.run – Agent sandbox with a transactional, versioned filesystem"

ozkatz — Thu, 07 May 2026 01:15:10 +0000

S3 offers versioning at the single file level.

Imagine an agent dropping a directory with 1m images in it. just figuring out what happened and what got dropped, restoring it one by one, etc. - doable, but ergonomics are a bit lacking.

New comment by ozkatz in "Show HN: Tilde.run – Agent sandbox with a transactional, versioned filesystem"

ozkatz — Wed, 06 May 2026 18:35:01 +0000

Regarding pricing - that's indeed a great question and we don't have an answer yet. It will very likely be based on consumption and should be competitive to similar solutions.

Atomic commits are based on snapshotting done by lakeFS under the hood. Each sandbox run produces a new atomic commit to a hidden "main" branch. Updating that branch is optimistically concurrent, with lakeFS checking for conflicts - multiple writers updating the same object.

New comment by ozkatz in "Show HN: Tilde.run – Agent sandbox with a transactional, versioned filesystem"

ozkatz — Wed, 06 May 2026 18:32:44 +0000

It uses lakeFS under the hood, so the unit of conflict would be a single file (object, under the hood). Resolving conflicts requires "picking" a winning side, or rerunning a conflicting job. Would you see a use case for merging changes into the same file? Interested to hear about your use case!

New comment by ozkatz in "Show HN: Tilde.run – Agent Sandbox with a Transactional, Versioned Filesystem"

ozkatz — Wed, 06 May 2026 18:30:46 +0000

It provides a filesystem abstraction, which agents are really good at interacting with. Because it's just a POSIX filesystem - you can put a sqlite database directly on it and get those same transactional capabilities for that too.

New comment by ozkatz in "Show HN: Tilde.run – Agent Sandbox with a Transactional, Versioned Filesystem"

ozkatz — Wed, 06 May 2026 18:29:40 +0000

it should absolutely scale to that. The filesystem is backed by lakeFS, where every sandbox automatically branches out, and mounts that branch. so you get isolation from lakeFS and the scale of an underlying object store (S3, in Tilde).

New comment by ozkatz in "Show HN: Tilde.run – Agent sandbox with a transactional, versioned filesystem"

ozkatz — Wed, 06 May 2026 18:28:28 +0000

If that database is stored on the transactional filesystem available to the sandboxes, yes! Instead of backing up, it utilizes an efficient snapshot mechanism (lakeFS under the hood).

New comment by ozkatz in "Show HN: Tilde.run – Agent Sandbox with a Transactional, Versioned Filesystem"

ozkatz — Wed, 06 May 2026 18:27:31 +0000

Part of the appeal (subjective, I know) of versioning is stuff like human-in-the-loop approvals. Think of a pull request: a change is requested by an agent, a human approves, changes get merged atomically. Even if other changes were applied since creation.

New comment by ozkatz in "Show HN: Tilde.run – Agent Sandbox with a Transactional, Versioned Filesystem"

ozkatz — Wed, 06 May 2026 18:25:55 +0000

Hey! It doesn't necessarily have to be "data heavy", but any form of state (from code to binary files) that an agent might use for automation.

Agents are really good at interacting with files and directories (text in, text out!). This adds a layer for those that allows managing that state in a transactional, versioned way.

New comment by ozkatz in "Show HN: Tilde.run – Agent sandbox with a transactional, versioned filesystem"

ozkatz — Wed, 06 May 2026 18:23:21 +0000

Oh VMS, How I miss thee

New comment by ozkatz in "Show HN: Tilde.run – Agent Sandbox with a Transactional, Versioned Filesystem"

ozkatz — Wed, 06 May 2026 17:28:54 +0000

In a perfect world, every system and external API would expose a standardized interface for versioning its own immutable state, so you'd be able to rollback and time travel across multiple such systems.

Not sure what else we can do in this world other than tightly control outbound requests and provide enough visibility into those requests for a human|agent to try and undo changes.

Happy to hear your thoughts - what would you like to see us take this?

New comment by ozkatz in "Show HN: Tilde.run – Agent Sandbox with a Transactional, Versioned Filesystem"

ozkatz — Wed, 06 May 2026 17:20:30 +0000

oz dot katz at treeverse.io would be best. ICP is SMB/mid-sized ISVs.

New comment by ozkatz in "Show HN: Tilde.run – Agent Sandbox with a Transactional, Versioned Filesystem"

ozkatz — Wed, 06 May 2026 17:09:49 +0000

not at the moment. You can use lakeFS directly with Fuse-Mount to do something similar with your own compute.

New comment by ozkatz in "Show HN: Tilde.run – Agent sandbox with a transactional, versioned filesystem"

ozkatz — Wed, 06 May 2026 17:09:20 +0000

Currently a static 2 cores and 4GB RAM, no GPU. Will be configurable soon!

New comment by ozkatz in "Show HN: Tilde.run – Agent Sandbox with a Transactional, Versioned Filesystem"

ozkatz — Wed, 06 May 2026 17:06:15 +0000

Exactly that!

New comment by ozkatz in "Show HN: Tilde.run – Agent Sandbox with a Transactional, Versioned Filesystem"

ozkatz — Wed, 06 May 2026 17:00:51 +0000

Much appreciated! and good luck with your project