# NousResearch/hermes-agent · Show elapsed time in CLI/TUI prompts

## Open now

- Nothing open on GitHub.

These items relate to displaying elapsed time information in the CLI prompt and TUI interface, including time since the last user message and turn duration. The work spans both the command-line prompt and a ticker/status line component.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #13105. Verify it addresses your case.
- **Recommended:** read PR #13105 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-13105`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #8541: Feature: show elapsed time since last user message in CLI prompt

## Prior & competing PRs

- **#13105: feat(tui): turn elapsed in FaceTicker + done-in sys line on turn end (#8541)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `ui-tui/src/app/interfaces.ts`, `ui-tui/src/app/useMainApp.ts`, `ui-tui/src/components/appChrome.tsx`, `ui-tui/src/components/appLayout.tsx`
- **#8588: feat(cli): show elapsed time in the prompt**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`

## Fix status

- Merged to main in PR #13105 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-04-20`. This confirmation is old and may be out of date (a revert/reopen would not have invalidated it here); re-verify.