This seems super useful for pairing and multiple machine work.
Honestly I wish something like this could replace git, but my guess is you’d need to build specialized editors for this. In the direction of: https://www.inkandswitch.com/upwelling/
I was wondering if I could use this for multiple processes (codex, nvim) on the same machine, but then I realized this use case is unnecessary (brain fart).
> 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.
This is super cool!
This seems super useful for pairing and multiple machine work.
Honestly I wish something like this could replace git, but my guess is you’d need to build specialized editors for this. In the direction of: https://www.inkandswitch.com/upwelling/
I was wondering if I could use this for multiple processes (codex, nvim) on the same machine, but then I realized this use case is unnecessary (brain fart).
> 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.