Sandbox Smoke-Test Workspace
An agent-cloud / automation platform (OSS components)
Overview
A throwaway smoke-test workspace used to validate the platform’s agent sandbox runtime, a minimal Bun HTTP server deployed into a sandbox to confirm that a workspace boots, serves, and hot-reloads.
Why It Exists
When iterating on the sandbox runtime you need the smallest possible workload that exercises the deploy-and-run path. This is that fixture: a one-route web server that proves the environment, startup script, and live-reload all work.
What We Built
A tiny workspace defined by a chucky.json manifest, a startup.sh that launches bun --hot --watch http.js, an http.js using Bun.serve to serve a single index.html route on port 4321 with HMR enabled, and a .chucky workspace config. No application logic beyond the smoke test.
Technologies & Approach
Bun’s built-in HTTP server and hot-reload, run inside the platform’s sandbox via its workspace manifest and startup hook, chosen for the fastest possible boot and edit-reload loop.
Outcome / Impact
Served as a quick reproducible check that the sandbox runtime correctly provisions a workspace and runs a live-reloading server; an internal R&D/testing artifact rather than a shipped product.
Capabilities Demonstrated
- Minimal reproducible workspace for runtime smoke-testing
- Bun-based hot-reloading dev server in a cloud sandbox