feat(tui): turn elapsed in FaceTicker + done-in sys line on turn end (#8541)#13105
Merged
Conversation
…8541) StatusRule now renders `{sinceLastMsg}/{sinceSession}` (e.g. `12s/3m 45s`) when a user has submitted in the current session; falls back to the total alone otherwise. Wires `lastUserAt` through the state/session lifecycle: - useSubmission stamps `setLastUserAt(Date.now())` on send - useSessionLifecycle nulls it in reset/resetVisibleHistory - /branch slash nulls it on fork
…edge Status bar ticker was too hot in peripheral vision. The moment the elapsed value matters is when the prompt returns — so surface it there. Dim `fmtDuration` next to the GoodVibesHeart, idle-only (hidden while busy), so quick turns and active streaming stay quiet.
Collaborator
Author
|
Moved the display: the
Latest commit: 9910681 |
Drops `lastUserAt` plumbing and the right-edge idle ticker. Matches the
claude-code / opencode convention: elapsed rides with the busy indicator
(spinner verb), nothing at idle.
- `turnStartedAt` driven by a useEffect on `ui.busy` — stamps on rising
edge, clears on falling edge. Covers agent turns and !shell alike.
- FaceTicker renders ` · {fmtDuration}` while busy; 1 s clock for the
counter, existing 2500 ms cycle for face/verb rotation.
- On busy → idle, if the block ran ≥ 1 s, emit a one-shot
`done in {fmtDuration}` sys line (≡ claude-code's `thought for Ns`).
Collaborator
Author
|
Iteration: pivoted away from the persistent idle-edge counter. Neither ~/claude-code nor opencode expose one (both fold elapsed into the busy indicator and drop it at idle). This PR now matches that convention.
Implementation: Latest: 2de1aad |
The transcript line was noisy. Keep the one thing the issue really needs: live elapsed next to the busy verb.
ulasbilgen
pushed a commit
to ulasbilgen/hermes-adhd-agent
that referenced
this pull request
May 1, 2026
…d-lastmsg-8541 feat(tui): turn elapsed in FaceTicker + done-in sys line on turn end (NousResearch#8541)
aj-nt
pushed a commit
to aj-nt/hermes-agent
that referenced
this pull request
May 1, 2026
…d-lastmsg-8541 feat(tui): turn elapsed in FaceTicker + done-in sys line on turn end (NousResearch#8541)
Luminet2023
pushed a commit
to Luminet2023/hermes-agent
that referenced
this pull request
May 1, 2026
…d-lastmsg-8541 feat(tui): turn elapsed in FaceTicker + done-in sys line on turn end (NousResearch#8541)
02356abc
pushed a commit
to 02356abc/hermes-agent
that referenced
this pull request
May 14, 2026
…d-lastmsg-8541 feat(tui): turn elapsed in FaceTicker + done-in sys line on turn end (NousResearch#8541)
gweeteve
pushed a commit
to gweeteve/hermes-agent
that referenced
this pull request
Jun 2, 2026
…d-lastmsg-8541 feat(tui): turn elapsed in FaceTicker + done-in sys line on turn end (NousResearch#8541)
Egavasyug
pushed a commit
to Egavasyug/hermes-agent
that referenced
this pull request
Jun 10, 2026
…d-lastmsg-8541 feat(tui): turn elapsed in FaceTicker + done-in sys line on turn end (NousResearch#8541)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #8541.
Summary
Adds a lightweight timer next to the existing session duration:
{sinceLastMsg}/{sinceSession}(e.g.12s/3m 45s). Renders in the status bar's existing│ 3m 45sslot, so no new chrome. When no user message has been submitted yet in this session, just the total renders (unchanged behavior).How it wires
useMainAppholdslastUserAt: null | number, threaded intoappStatus.useSubmission.sendstampssetLastUserAt(Date.now())alongsidesetLastUserMsg.useSessionLifecycle.resetSession/resetVisibleHistorynull it;/branchslash nulls it on fork (/tools enablegoes throughresetVisibleHistory→ free).SessionDurationcomponent extended to optionally render the leading segment.Test plan
npm run type-check— cleannpx vitest run— 15/15 files, 98/98 tests passhermes --tui, send a message, wait; status bar shows12s/42setc; second submit resets the left counter;/newresets both; narrow terminals truncate cleanly (existingwrap="truncate-end"on the left cluster).