Summary

The Control UI Sessions tab currently initializes with an unbounded activeMinutes filter and a default limit of 120. On instances with a larger session history, this can make the first sessions.list call scan too much history and periodically block the gateway/UI for several seconds.

A safer default is to load recent sessions only and keep the filter editable for users who need older history.

Observed locally

On a long-running local OpenClaw gateway, Control UI sessions.list calls before bounding were frequently slow:

• 24567ms
• 24571ms
• 28344ms
• 24492ms
• repeated ~6000ms calls

After applying a local source-equivalent hotfix and cache-busting the served UI bundle, the first bounded call was lower and subsequent calls were fast:

• 4019ms initial post-reload call
• 112ms
• 508ms

Expected behavior

The default Control UI Sessions view should avoid expensive full-history reads while preserving access to older sessions via user-editable filters.

Proposed fix

Initialize the Sessions tab filters to:

• activeMinutes = "120"
• limit = "50"

This keeps the default query bounded without changing the API or removing user access to older sessions.

Notes

This is intentionally a UI default change only. Users can still widen/clear filters in the Sessions tab when they need broader history.