Automated CodeSandbox Workspace Inventory
Every Monday, WebRun signs into CodeSandbox, lists every sandbox and devbox in your team workspace with its owner, privacy setting, and last update date, saves the inventory as a dated file in Google Drive, and sends you a WhatsApp summary naming the ones nobody has touched in 90 days so you can decide what to archive.
How do I audit which sandboxes my team still uses?
WebRun inventories your CodeSandbox team workspace every Monday, listing each sandbox and devbox with its owner, privacy setting, and last update date. It saves a dated file to Google Drive and sends you a WhatsApp summary of anything dormant for 90 days or unexpectedly public, so cleanup decisions get made with facts.
- Dormant sandboxes get reviewed instead of accumulating forever
- Unexpectedly public sandboxes surface within a week
- Drive holds a dated inventory you can diff across months
Built for engineering managers · frontend teams · platform teams · agencies
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
codesandbox.io/signinin a real browser with your saved login - no setup, no API keys. -
1
CodeSandbox - list every sandbox and owner
codesandbox.io
WebRun opens CodeSandbox to list every sandbox and owner. - Sign into CodeSandbox and open your team workspace
- List every sandbox and devbox with its name, owner, privacy setting, and last update date
- Mark anything public, anything with no owner listed, and anything untouched for more than 90 days
Done when Every sandbox in the workspace is listed with owner, privacy, and last update.
-
2
Google Drive - save the dated inventory
drive.google.com
WebRun opens Google Drive to save the dated inventory. - Create a dated inventory file in your engineering housekeeping folder
- Write one row per sandbox with name, owner, privacy, last update, and days dormant
- Add a summary block with the totals for active, dormant, and public sandboxes
Done when This week's inventory file is saved in Google Drive.
-
3
WhatsApp - flag the dormant ones
whatsapp.com
WebRun opens WhatsApp to flag the dormant ones. - Send a short message listing sandboxes untouched for 90 days with their owners
- Call out anything set to public that looks like internal work
- Include the link to the Google Drive inventory and leave the archive decision to a human
Done when You have this week's dormant and public sandbox list on WhatsApp.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it delete or archive sandboxes?
No. WebRun only lists what exists and flags what looks dormant. Deleting, archiving, or changing a sandbox is always a human decision made inside CodeSandbox.
Does it read my code?
No. It reads the workspace listing: names, owners, privacy settings, and last update dates. It does not open files or copy source into the inventory.
Why does it flag public sandboxes?
Because a sandbox left public can expose internal work or keys. The list simply names them so a human can check whether each one is meant to be public.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.