Rivet Agents: durable actors and a sandbox controller for coding agents

The rivet-dev/agents repository collects agent infrastructure from Rivet, organized around one problem: keeping an agent process alive and controllable across restarts, rather than treating each run as ephemeral. The README frames the work as durable Rivet Actors and sandboxed execution, with separate packages for each approach. Two projects share the repo. Rivet Agents, in packages/ with docs in docs/, runs agents such as Pi as durable Rivet Actors; the named packages are @rivet-dev/pi and @rivet-dev/sandbox-adapter. Sandbox Agent, in sandbox-agent/, runs coding agents in sandboxes and controls them over HTTP. That split matters for design: the actor path is for agents that need persistent identity and state, while the sandbox path is for isolating coding work and driving it through a network interface. Readiness signals in the README The clearest evidence is release discipline. Everything ships on one version line: just release runs scripts/release/ to bump every package, publish crates and npm packages, upload binaries, and tag