Skip to content

Session pages show a generated run summary and tab counts

When a run finishes, Everruns writes a one-sentence summary of what it did, or which step failed and why, and shows it under the session title instead of the start time. The summary is also on the session as run_summary. It needs a utility model (UTILITY_* keys); without one, the header keeps the start time. Summary spend does not count against the session budget.

The Work, Events and Workspace tabs now carry counts. Empty tabs show no badge, and large counts are shortened, for example 12.4K.

See Web UI, Environment variables, #3260 and #3266.