Automated Coder Idle Workspace Cost Alerts
Every morning, WebRun opens Coder, reviews workspace activity across the team, texts the admin when a workspace has sat idle with no connection for more than three days, and saves a usage report to Google Drive so idle compute does not quietly run up the bill.
How do I catch idle Coder workspaces before they waste compute cost?
WebRun reviews Coder workspace activity every morning, texting the admin the moment a workspace has sat idle with no connection for three days. It also saves a dated usage report to Google Drive for trend tracking, so idle compute gets caught and reported before it quietly runs up the infrastructure bill.
- Idle workspaces get caught within a day instead of running for weeks unnoticed
- The admin gets a direct text instead of digging through a usage dashboard
- A saved weekly report makes usage trends easy to spot over time
Built for Platform engineering teams · infrastructure admins · engineering managers · cost-conscious dev teams
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
coder.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Coder - review workspace activity
- Open Coder and review workspace activity across the team
- Check the last connection time for each workspace
- Flag any workspace with no connection in the last three days
Done when Every idle workspace is identified with its owner and days idle.
-
2
Twilio - text the admin about idle workspaces
twilio.com
WebRun opens Twilio to text the admin about idle workspaces. - Send a text to the platform admin for each idle workspace
- Include the workspace owner and how many days it has sat idle
- Keep the message to a single line per workspace
Done when The admin has been texted about every workspace idle more than three days.
-
3
Google Drive - archive the usage report
drive.google.com
WebRun opens Google Drive to archive the usage report. - Open the Coder Usage Reports folder in Google Drive
- Save a dated report listing all workspaces with their idle status and last connection date
- Keep the last eight weekly reports for trend comparison
Done when A dated usage report is saved in Google Drive.
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 WebRun stop or delete the idle workspace?
No. It only flags idle workspaces and reports on them. Stopping or deleting a workspace stays a decision made by the admin or the workspace owner.
What counts as idle?
No connection to the workspace for three consecutive days. That threshold can be tuned to match how your team actually works.
Does the text go to the workspace owner or the admin?
The admin, so cost and capacity decisions stay with whoever manages the Coder deployment rather than paging every individual developer.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.