Skip to content

fix(tui): scroll to bottom on submit, space above busy indicator - #26

Merged
jkyberneees merged 2 commits into
mainfrom
fix/submit-scroll-status-spacing
Aug 9, 2026
Merged

fix(tui): scroll to bottom on submit, space above busy indicator#26
jkyberneees merged 2 commits into
mainfrom
fix/submit-scroll-status-spacing

Conversation

@jkyberneees

Copy link
Copy Markdown
Contributor

What

  • Scroll fix: pressing Enter (new prompt, or queueing mid-turn) now always jumps the transcript to the bottom so the submitted message is visible. Previously refresh() only stuck to the bottom when already there, so submitting while reading scrollback left the new input out of view. Streaming events keep the old stick behavior — no yanking readers around.
  • Spacing: the busy activity indicator (🧠 thinking / tool progress) gets a blank separator row above it, between the transcript and the input box. inputAreaHeight() accounts for the extra row so the layout math stays exact.

Tests

  • New TestSubmitJumpsToBottom: scrolled-up viewport, submit fresh and mid-turn-queue, asserts AtBottom().
  • TestStatusLinePlacement updated for the two-row status line cost and the leading blank row.
  • make fmt && make vet && make lint && make test — all green (lint 0 issues, race-enabled suite).

refresh() only sticks to the bottom when already there, so hitting Enter
while reading scrollback left the new message out of view. Submitting is
an explicit 'show me the latest' signal: GotoBottom on send, and on the
mid-turn queue path for consistency.
Gives the thinking/tool indicator breathing room between the transcript
and the input box; inputAreaHeight accounts for the extra row so the
layout math stays exact.
@jkyberneees
jkyberneees merged commit 016e62c into main Aug 9, 2026
5 checks passed
@jkyberneees
jkyberneees deleted the fix/submit-scroll-status-spacing branch August 9, 2026 12:47
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