ChatGPT Containers just got markedly more capable inside the sandbox. They now execute Bash directly, run JavaScript and other languages alongside Python, install packages with pip or npm via a proxy, and download files for local processing. Outbound network requests remain blocked, which keeps the boundary clear while still enabling real workflows. The sharp downside is sparse documentation, which leaves developers to discover features piecemeal. 🧰 simonwillison.net
Why this matters: for years, coding with assistants felt like pseudo‑REPLs with limited IO. Direct shell access and package management turn the environment into a practical scratchpad for data work, scripting, and multi‑language experiments. The new container.download capability bridges web files into the sandbox so users can analyze artifacts without opening their machine. This compresses setup time from hours to minutes, especially for quick prototypes or debugging sessions. ⚙️ simonwillison.net
Risk and governance do not vanish with convenience. The proxy path for installs raises questions about provenance and reproducibility, and thin docs create operational ambiguity for teams that need repeatable steps. With no outbound network, the model encourages curated inputs and explicit downloads, which is safer but still requires process discipline. Clear release notes, examples, and policy guardrails would unlock these gains for larger organizations without surprise behavior. 🔒 simonwillison.net