Repository navigation
Pin the input editor while scrolling back through transcript history #1049
Description
Feature Description
I'd like the input box to stay at the bottom of the screen while I scroll back through the
transcript, so I can keep reading and type at the same time. While I'm scrolled up, new output
shouldn't pull me back down; a "jump to latest" affordance when I'm ready to follow again
would be perfect.
I assume this happens because the TUI uses the terminal's normal scrollback. I don't want to
take that away from people who like it, so an opt-in fullscreen mode would be fine: the
transcript scrolls inside the app, and the prompt and status stay pinned.
Use Case
What I usually do is scroll up to re-read an earlier part of the conversation so I can refer
back to it in my next message. The moment I start typing, the view jumps to the bottom, so I lose the spot
I was reading. Then I scroll up again, find it again, and repeat.
Additional Context
For reference, pi's fullscreen mode already works this way. I looked at the mod API and don't
think a mod can reach this, since mods can't take over the screen, so I'm filing it as a core
feature request.
Environment: Command Code 1.84.0 on Windows 11, tested in Windows Terminal and the VS Code
integrated terminal.
How important is this to you?
Important for my workflow
Activity
vipulgupta2048 commentedon Oct 21, 2026
Thanks for reaching out @Tibbee A valid DX concern but one that agreeably might be questionable. UNIX terminals have always scrolled back down once you start typing which is what we are following at Command Code CLI as well.
For your workflow, I could recommend using
ctrl + gto open the prompt you are writing in the editor window when you are using it inside VS Code integrated terminal as you mentioned.This will allow you to scroll up to any point and still be able to cross reference the agent's output in your next prompt. I use that a lot nad it's very helpful. Hope it helps!
xinpengdr commentedon Oct 21, 2026
Also asking for this, but specifically as an opt-in TUI setting rather than a default behavior change.
Concrete ask: a config key (e.g.
tui.fullscreen, exposed in/configand persisted in~/.commandcode/config.json) that switches the TUI to an in-app transcript viewport:--fullscreenflag and/or keyboard toggle for per-session useWhy the opt-in framing matters: in #453 the objection to the alternate screen was that terminal search and scrollback get worse. Keeping the current renderer as the default and making fullscreen an explicit switch avoids forcing that tradeoff on everyone.
Worth covering in the implementation, if it lands:
Environment: Command Code 1.86.3 on macOS.