Overview

Customers are frustrated by the lack of configurability in how Autostop responds to user activity. Since #10704, user activity bumps the initial TTL by 1 hour, preventing them from leaving their workspaces for extended periods.

To remedy this, we plan to introduce a new configurable "Inactivity timer" that lets users set how many hours their TTL is extended by when they are active in their workspace.

Defaults to the current implementation of 1-hour bumps.

Just like the existing activity bump, this inactivity timer should not override quiet hours or Autostop requirement.

Product Requirements

• Users can configure the number of hours activityBump adds to TTL
• N hours configurable in UI/CLI/API
• Template settings propagate down to users
• Defaults to 1 hour, preventing disruption of current behavior