Skip to content

feat(tui): fade engine-event traces after 5s#8

Merged
jkyberneees merged 1 commit into
mainfrom
feat/tui-transient-notices
Jul 25, 2026
Merged

feat(tui): fade engine-event traces after 5s#8
jkyberneees merged 1 commit into
mainfrom
feat/tui-transient-notices

Conversation

@jkyberneees

Copy link
Copy Markdown
Contributor

Summary

  • Skill / memory / signal / subagent info traces previously stayed on screen for the entire session, piling up under the transcript.
  • Transient notices now carry an expiry timestamp and are swept 5 seconds after the most recent one (noticeTTL), via a tea.Tick timer batched into handleEvent; stale timers are ignored so fresh traces are never cut short.
  • Errors, disconnect, and server-log notices remain sticky.

Changes

  • internal/tui/model.go — parallel noticeExp slice, addTransientNote/pruneNotices/noticeTimer helpers, noticeExpireMsg handling.
  • internal/tui/view.gorenderNotices skips expired traces defensively; empty block no longer leaves a stray gap.
  • internal/tui/coverage_test.go — tests for the expiry sweep, stale-timer guard, and render filtering.

Verification

  • go build ./..., go vet ./internal/tui/, go test ./internal/tui/ all pass.

Skill, memory, signal, and subagent notices stuck around for the whole
session, cluttering the transcript. They now carry an expiry timestamp
and are swept 5s after the most recent trace; errors and disconnect
notices stay sticky.
@jkyberneees
jkyberneees merged commit cf6a867 into main Jul 25, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant