When a command is producing output fast, new lines can push earlier content out of view. Solo uses follow mode to decide whether the view stays pinned to live output or preserves your scroll position.
How follow mode works
Solo normally follows output while the main buffer is at the bottom. Opening terminal search deliberately pauses follow even at the bottom; closing search leaves it paused. Jump to bottom, or a real downward scroll that reaches the bottom, resumes follow. If an unconsumed user scroll moves the main-buffer viewport away from the bottom, follow turns off. With terminal mouse reporting active, the application consumes wheel input, so that wheel gesture does not move the viewport or turn follow off.
When follow mode is off, a Jump to bottom button appears near the lower-right corner of the terminal.
Returning to live output
To follow live output again:
- Click Jump to bottom.
- Or scroll back to the bottom. Solo resumes follow mode when a real downward scroll reaches the end.
Use cases
Reading a busy log without losing your place:
- Start a command that produces rapid output (e.g., a build with many steps, a verbose test run).
- Scroll up to find a specific log line you noticed.
- Follow mode turns off. Read without the view jumping.
- Click Jump to bottom when done.
Reviewing output after a crash:
If a command crashes mid-output, the terminal might have scrolled past the relevant error. Scroll up to find it; follow mode stays off so the crash message stays visible.
Alternate screen
Alternate-screen terminal apps, such as full-screen TUIs, force follow mode for that active screen. The persistent follow-mode state applies to the main buffer.
Limitations
- Follow mode only affects the display position. It does not pause or slow down the actual process.
- Main-buffer history is capped, so very old output can be pruned during high-volume runs.