Repository navigation
[FEATURE]: Show completion time and duration for every assistant turn in the TUI #53192
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
In the TUI, a prompt that runs several tool-call turns shows one footer, under the final message, with one number: the time since the prompt. The intermediate turns have no footer at all. So there is no way to see when a turn finished, or which step of a long run took the time.
Step 1: looking around.
✱ Glob "*.txt" (1 match)
Step 2: looking around.
✱ Glob "*.txt" (1 match)
All done, here is the final answer.
▣ Build · Fake · 15.8s
Proposal: a turn_timing option in tui.json with two independent booleans, both off by default so nothing changes unless you opt in:
time: when each assistant turn finished. Time of day if today, otherwise the date followed by the time (10/4/2026 11:26 PM).duration: how long each turn took. The final turn keeps the existing total since the prompt, labelledtotal.
✱ Glob "*.txt" (1 match)
▣ Build · Fake · 1:07 PM · 8.3s
Step 2: looking around.
✱ Glob "*.txt" (1 match)
▣ Build · Fake · 1:07 PM · 3.5s
All done, here is the final answer.
▣ Build · Fake · 1:07 PM · 3.7s · 15.6s total
They can be toggled at runtime with /turn-times and /turn-durations (also in the command palette, bindable). Like /timestamps, a toggled value persists in kv.json and wins over tui.json.
Related: #43243 (assistant timestamps only, tied to /timestamps), #35348 (start and completion timestamps for a run).
Reacted by Raphaël B and FyiurAmron
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Oct 4, 2026
This issue might be a duplicate of existing issues. Please check:
For keybind-related issues, please also check our pinned keybinds documentation: #4997
docs(forklog): record per-turn completion time and duration
FyiurAmron commentedon Oct 9, 2026
bump. needs to be implemented.
docs(forklog): record per-turn completion time and duration
opencodejr commentedon Oct 27, 2026
Thanks for the detailed proposal, @Nowaker! To restate it: you'd like an opt-in setting, with
/turn-timesand/turn-durationstoggles, that gives every assistant turn in a multi-step run its own footer with its completion time and duration, and keeps the total on the final turn.This isn't something a plugin can do today, because the TUI plugin API has no slot for each assistant message's footer. Maintainers will consider the feature.
Related issues:
/timestamps(no per-turn durations)gvtret commentedon Nov 11, 2026
+1 to this and PR #62530 — wall-clock completion time in assistant footers is the missing chronology anchor for long sessions. I work with multi-hour TUI sessions and regularly need to match agent actions against external logs; today the only way is a jq workaround over the session API. The PR's
session.timestamps/session.date_formatdesign looks like the right shape.