Stop idle Gitpod workspaces burning usage
Every hour, WebRun opens Gitpod, lists workspaces still in a running state past your idle threshold, captures the owner, repository, and idle time for each, opens a Trello card so the owner can stop it, and messages the platform team on WhatsApp.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I find Gitpod workspaces left running when nobody is coding?
Every hour WebRun opens Gitpod and lists the workspaces still running with nobody in them, reading the owner, the repository, and how long each has been idle. WebRun opens a Trello card per owner and messages the platform team on WhatsApp, so idle workspaces stop before they burn another day.
- Idle workspaces are named within the hour instead of at month end
- Every flagged workspace has an owner and a card, not just a number
- Nothing is stopped automatically, so uncommitted work stays safe
Built for platform engineers · engineering managers · DevOps teams · startup CTOs
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
gitpod.io/loginin a real browser with your saved login - no setup, no API keys. -
1
Gitpod - find idle running workspaces
WebRun opens Gitpod to find idle running workspaces. - Sign in to Gitpod and list every workspace currently in a running state
- Record the owner, the repository, and how long each workspace has been idle
- Keep only workspaces past the idle threshold you set, and skip anything running a prebuild
- Note the usage each idle workspace has consumed so far this billing period
- Stop nothing. WebRun reports idle workspaces so no uncommitted work is ever thrown away
Done when Every workspace past the idle threshold is listed with its owner and usage.
-
2
Trello - raise a card for the owner
WebRun opens Trello to raise a card for the owner. - Add a card to the platform board for each idle workspace found this hour
- Title it with the repository and the owner, and put the idle time and usage in the description
- Assign the card to the workspace owner so the person with the uncommitted work makes the call
Done when Every idle workspace has a Trello card assigned to its owner.
-
3
WhatsApp - alert the platform team
WebRun opens WhatsApp to alert the platform team. - Message the internal platform group with the count of idle workspaces and the usage at stake
- List the longest running ones first with their owners named
- Skip the message entirely on an hour with nothing idle
Done when The platform team knows what is idle right now and who owns it.
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 stop or delete workspaces on its own?
No. WebRun lists idle workspaces and assigns a card to the owner. Stopping a workspace is done by the developer, so uncommitted work is never lost to an automation.
How long does a workspace have to be idle to get flagged?
You set the threshold, and thirty minutes is a common starting point. Anything under it, and anything running a prebuild, is ignored.
Does it see my code?
No. WebRun reads the workspace list: owner, repository name, state, idle time, and usage. It does not open a workspace or read the code inside it.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.