The language-agnostic angle is the right reason to resurrect this. The original gym HTTP API was underrated for exactly that — being able to drive environments from Go or Rust without fighting Python interop was genuinely useful. Curious whether you're handling the render/visualize endpoints via server-sent events or polling. Streaming frame data over HTTP for visualisation can get messy fast, especially at higher framerates.