Proposal

I think we should resolve #2987 first as it affects how this feature is exposed to the template admin. Without templates as code, we can expose the feature in the same way as we do min_autostart_interval and max_ttl today.

Activity Rules

We should discuss which values we want to make knobs immediately. The more we lean into templates as code, the more configurable this can get.

For each of these events, bump the auto-stop by 1h:

• coder_app HTTP request
• DevURL HTTP request
• SSH access

Possible knobs:

• Bump amount
• Which coder_apps trigger bump
• Which access types trigger bumps

To help the user debug why their workspace isn't shutting down, we could add a tooltip to the UI that explains the last bump source. The options could be "Manual", <app name>, <dev url name>, or "SSH".

Pretty much all of our early scheduling feedback suggests that activity-based auto-stop should be enabled by default. So I propose that it is default with all of the knobs selected.

#3191 is user feedback that shows the value of combining schedule-based auto stop with activity-based auto-stop. If the user just wants activity-based, they can set the schedule to stop one hour after start.