Show per-message timestamps in Agent Mode for prompts and responses

[ryanentwarp]

Summary

Add per-message timestamps to Agent Mode so users can see when each prompt was sent and when the agent responded.

Problem

In Agent Mode, there is currently no way to see when a prompt was submitted or when the agent finished responding. For users who run long agent tasks or reference past conversations, the lack of timestamps makes it difficult to understand duration, sequence, and recency of interactions.

Reproduction steps or desired workflow

1. Open Agent Mode in Warp.
2. Send one or more prompts to the agent.
3. Desired: each user prompt and each agent response shows a timestamp (e.g., "5:47 AM" or a relative time like "2 min ago") so the user can tell when it was sent and how long the agent took to respond.

Artifacts

None attached.

Warp version

0.2026.04.25.08.29.00

Operating system

macOS 26.4

[oz-for-oss]

@ryanentwarp

Here's what I found while triaging this issue:

This looks like a feature request rather than a bug. Agent Mode appears to track timing data internally, but the conversation UI does not currently expose per-message timestamps.

I have a few follow-up questions before I can narrow this down:

1. Would you prefer these timestamps to be always visible in the conversation, or shown on hover/tooltip to reduce visual clutter?
2. For agent responses, would the most useful display be the response start time, finish time, elapsed duration, or a combination?

Reply in-thread with those details and the triage workflow will automatically re-evaluate the issue and update the diagnosis, labels, and next steps.

Maintainer details

I concluded that feature request to add visible per-message timestamps to Agent Mode prompts and responses..

Triage summary

This is an enhancement request for Agent Mode: show visible timestamps for user prompts and agent responses so long-running or historical conversations have clearer timing context.

Reproducibility

High. The requested behavior can be checked with a normal Agent Mode conversation: current prompt and response rendering does not display per-message sent or finished times.

Likely implementation area

Agent Mode exchanges already carry timing metadata, including exchange start/finish times and server message timestamps, and related code uses timing data for history, duration, and telemetry. The gap appears to be in the Agent Mode block UI render path, which renders query/output content without exposing those timestamps.

Duplicate check

I checked open issues with pagination. Existing timestamp-related requests mostly cover terminal commands/lines or long-running shell command counters, not per-message Agent Mode prompts and responses, so this is not marked as a duplicate.

Question reasoning

1. Would you prefer these timestamps to be always visible in the conversation, or shown on hover/tooltip to reduce visual clutter? — This is a product/UX preference the codebase cannot infer, and it would affect the visual design and implementation scope.
2. For agent responses, would the most useful display be the response start time, finish time, elapsed duration, or a combination? — The implementation could surface several existing timing values, and the reporter's workflow can clarify which one best solves the problem.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz