> I was wondering if I could use this for multiple processes (codex, nvim) on the same machine
Could be useful for time-travel I suppose (in the same sense that git is, even if the repo only exists machine local). Right now that isn't very developed in opbox, other than the ability to clone an existing workspace at a particular historical moment (ob clone --as-of "2026-07-03T22:00:00-07:00"), but could be neat to "rewind" a workspace to any prior save state automatically.
> it leaves me completely baffled about what s2 does, what problem s2 is trying to solve, or who the intended audience of s2 is
Regarding S2 generally (not just s2-lite), the intent behind it is to turn the core data structure from streaming platforms (like Kafka) into a serverless primitive -- kinda similar to what object storage did for file storage.
So if you are already in the world of working with streaming platforms, S2 gives you a simpler API, bottomless storage (S2 itself uses object storage for durability), and no limits on the quantity of streams you can create and work with. Streams also all have URIs and are directly accessible over REST with granular access controls.
This enables new types of patterns for working with streams, other than just the traditional ones where people typically reach for streaming platforms (like CDC, ETL pipelines, etc). An agent can have its own stream to serialize state onto, for instance; you can use a stream as a durable transport layer -- e.g., you want to reliably provide a flow of data (tokens from a model, financial ticker data, etc) to a user and allow them to resume from exactly where they left off if they are disconnected, for instance; you could use streams as a durable ingest buffer, for collecting data that will eventually reside in an OLAP like Clickhouse.
I'm a huge fan of Asciinema, and this is awesome work.
Regarding the live streaming feature, I hacked a similar thing on top of s2.dev streams[1] (disclaimer: I am a co-founder), which could alleviate the need for a relay in this architecture[2]. Naturally showing off `btop` was the highlight for me as well :-D.
Could be useful for time-travel I suppose (in the same sense that git is, even if the repo only exists machine local). Right now that isn't very developed in opbox, other than the ability to clone an existing workspace at a particular historical moment (ob clone --as-of "2026-07-03T22:00:00-07:00"), but could be neat to "rewind" a workspace to any prior save state automatically.