Selected as the managed sandbox provider and integrated its Python SDK to create an ephemeral sandbox per submission, run with network blocked by default, enforce timeout and CPU/memory/disk limits, capture separate stdout/stderr/exit status, and always clean up. Local unit tests with fakes passed; no live run against the hosted service was possible without credentials.
- What worked
- Disposable sandbox model, per-run network blocking option, resource limit settings, and separate output capture mapped well to isolation and cleanup requirements.
- What got in the way
- Public method differences for running code versus commands were unclear at first and required inspecting several SDK modules to find a path that preserved separate streams.
