Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Dashboard Sessions view: no live/active indicator, 'Active N' label is misleading [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#78307•Fetched 2026-05-07 03:38:29
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
2
Author
SigmundSigmundSigmundSigmund
Participants
clawsweeper[bot]clawsweeper[bot]SigmundSigmundSigmundSigmund
Timeline (top)
commented ×1

The dashboard Sessions view at http://127.0.0.1:18789/ doesn't surface whether a session is currently running vs dormant. The Active N filter sounds like "only show currently active" but is actually a lookback window in minutes — so with Active 120 the user sees every session updated in the last 2 hours, with no way to tell which (if any) is processing a turn right now.

Root Cause

The dashboard Sessions view at http://127.0.0.1:18789/ doesn't surface whether a session is currently running vs dormant. The Active N filter sounds like "only show currently active" but is actually a lookback window in minutes — so with Active 120 the user sees every session updated in the last 2 hours, with no way to tell which (if any) is processing a turn right now.

RAW_BUFFERClick to expand / collapse

Summary

The dashboard Sessions view at http://127.0.0.1:18789/ doesn't surface whether a session is currently running vs dormant. The Active N filter sounds like "only show currently active" but is actually a lookback window in minutes — so with Active 120 the user sees every session updated in the last 2 hours, with no way to tell which (if any) is processing a turn right now.

Repro

  1. Open the dashboard, click Sessions.
  2. Note the Active 120 filter at the top.
  3. With several recent sessions (parents, completed subagents, abandoned /new sessions), the list shows ~6 entries.
  4. No column or badge indicates which is live.

Why it matters

  • Users can't tell if a stalled-looking turn is actually still processing somewhere.
  • After provider timeout cascades or /new mid-turn, abandoned sessions linger and look identical to the live one.
  • The data already exists: sessions_list (tool) returns status: "running" in its JSON; the UI just doesn't render it.

Suggested fix

Either (or both):

  • Add a Status column (running / idle / ended) populated from the existing status field.
  • Add a Live only toggle that hides anything not currently processing a turn.

Bonus: rename the Active N control to something like Updated within N min to remove the false-active connotation.

Environment

  • OpenClaw: latest as of 2026-05-05
  • macOS Darwin 25.4.0 arm64
  • Node v25.8.0
  • Webchat surface, dashboard at 127.0.0.1:18789

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#memory management#API rate limit#retriever error#indexing error#inference speed

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Dashboard Sessions view: no live/active indicator, 'Active N' label is misleading [1 comments, 2 participants]