openclaw - 💡(How to fix) Fix Show message timestamps and completed agent runtime in detail mode [2 comments, 1 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#72316Fetched 2026-04-27 05:31:41
View on GitHub
Comments
2
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
commented ×2closed ×1
RAW_BUFFERClick to expand / collapse

Request

In detail mode, expose more timing information for agent runs:

  1. Show message timestamps in the detailed transcript/view.
  2. After an agent run finishes, show how long the agent was working for / total elapsed runtime.

Why

This makes it easier to understand when each message/event happened and how long a completed agent turn actually took, especially for longer-running/background work.

Notes

Suggested UX wording can be simple, e.g. a timestamp on each detailed message and a final completed-run duration such as worked for 3m 42s / elapsed 3m 42s.

extent analysis

TL;DR

Exposing timing information for agent runs can be achieved by modifying the detailed transcript/view to include message timestamps and calculating the total elapsed runtime after an agent run finishes.

Guidance

  • To show message timestamps, consider adding a timestamp field to each message object in the detailed transcript/view.
  • Calculate the total elapsed runtime by recording the start and end times of each agent run and displaying the difference.
  • Update the UI to display the timestamp for each message and the total elapsed runtime after an agent run finishes, using suggested UX wording such as "worked for X" or "elapsed X".
  • Ensure the timing information is accurately calculated and displayed in a user-friendly format.

Example

// Example of calculating elapsed runtime
const startTime = new Date();
// Agent run code here
const endTime = new Date();
const elapsedRuntime = (endTime - startTime) / 1000; // in seconds
const minutes = Math.floor(elapsedRuntime / 60);
const seconds = Math.floor(elapsedRuntime % 60);
console.log(`Worked for ${minutes}m ${seconds}s`);

Notes

The exact implementation details may vary depending on the programming language and framework used. This guidance assumes a basic understanding of date and time calculations.

Recommendation

Apply workaround: Modify the existing code to include timing information, as the issue does not imply a need for a version upgrade.

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…

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 Show message timestamps and completed agent runtime in detail mode [2 comments, 1 participants]