openclaw - 💡(How to fix) Fix [Bug]: Phantom session persists in Recent sidebar despite being completed; timestamp falsely updates

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Title: Phantom session persists in Recent sidebar despite being completed; timestamp falsely updates

Description:

A completed subagent session continues to appear in the Recent sidebar with an updating timestamp, even though the backend shows it as done.

Session Details:

Display name: webchat:g-agent-main-das (truncated, full label: admin-dashboard-build)
Session key: agent:main:subagent:6198a300-.....3c
Actual status: done (completed 2026-05-20)
Backend updatedAt: 1778488770403 (old timestamp)

DevTools Errors (possibly related):

Content-Security-Policy: The page's settings blocked a JavaScript eval (script-src)... Uncaught (in promise) TypeError: ServiceWorker script at ... encountered an error during installation. Source map error: Error: request failed with status 404

Steps to reproduce

Complete a subagent session (in my case: admin dashboard build) Return to main session Observe completed session still appears in Recent sidebar Note timestamp updates periodically (was 31 min ago, now shows 4 min ago, etc.) No actual activity in that session per backend

Expected behavior

Completed sessions should either:

Not appear in Recent, OR
Show accurate "last active" time from when they actually ended

Actual behavior

Phantom entry with falsely updating timestamp persists.

OpenClaw version

OpenClaw version: 2026.5.20-e510042870cf

Operating system

W10, Browser: Firefox (latest)

Install method

npm

Model

Kimi-2.5

Provider / routing chain

Browser → OpenClaw Gateway (self-hosted) → Venice.ai API → Kimi K2.5

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Backend Evidence — Session Actually Completed:

Backend query sessions_list(activeMinutes=10) returns only 1 session (current), confirming the phantom session has no actual recent activity.

DevTools Errors:

Content-Security-Policy: The page's settings blocked a JavaScript eval (script-src) from being executed...
Uncaught (in promise) TypeError: ServiceWorker script at http......

Impact and severity

No response

Additional information

DevTools Errors (possibly related):

Content-Security-Policy: The page's settings blocked a JavaScript eval (script-src)... Uncaught (in promise) TypeError: ServiceWorker script at ... encountered an error during installation. Source map error: Error: request failed with status 404