$ cat ~/map/pi-conversation-outline.md
pi-conversation-outline
Read-only outline rail for fullscreen: one tick per prompt, hover to preview, click to jump.
extensions✓ Sep 18
Facts
- GitHub Stars
- ★ 1
- Forks
- 0
- license
- MIT
- npm / mo
- —
- last push
- Sep 23, 2026
install
Run pi install npm:pi-conversation-outline (or pi install git:github.com/youxia-2025/pi-conversation-outline); needs tuiMode fullscreen, which is pi's current default, then /reload or a fresh session## TL;DR
A read-only outline rail for pi's fullscreen TUI: one tick per user prompt along the right edge, hover previews the question, click jumps to that turn, and nothing about the conversation is rewound, forked, or changed.
## Key points
- $Read-only end to end: the rail renders only the current root-to-leaf branch of the conversation, never rewinds or forks, and changes no context; previews show the first line of each prompt only, without tool traces or thinking.
- $Navigation: one tick per user prompt in conversation order rather than scroll proportion, the turn at the top of the viewport highlighted, up and down arrows step between turns, hover shows the preview, click jumps to that prompt, and Ctrl+Alt+O toggles the rail.
- $Visibility conditions: the rail appears in fullscreen mode (pi's current default) once the terminal is at least 60 columns wide and two or more prompts exist; regular mode has no in-app mouse, so the rail does not appear there.
- $An honest compatibility warning: the extension reaches into undocumented pi TUI structures — the conversation ScrollView, the gutter, and the nonCapturing overlay — so a major pi update can break it; the failure mode is a missing or misjumping rail, and pi remove npm:pi-conversation-outline is the documented way out.
- $Coexistence with tool-card extensions: alongside Claude Code-style tool-card packages that touch hasOverlay or folded-card clicks, the rail narrows hasOverlay to overlays that grab input and blocks the native single-click toggle so the two do not fight over the mouse; without such extensions installed, these patches are no-ops.
- $Development: npm test covers the extension, and pi -e ./extensions/index.ts runs it locally without writing settings.
## FAQ
Q Does jumping between turns change the conversation?
No — the rail is read-only. It never rewinds, forks, or edits context; a click only moves your view to that prompt, along the current root-to-leaf branch.
Q Why does the rail not appear in my session?
It needs fullscreen TUI mode, a terminal at least 60 columns wide, and at least two user prompts. Regular mode has no in-app mouse support, so the rail stays hidden there.
Q What happens when a pi update breaks it?
The README says so plainly: the extension uses undocumented pi TUI structures, so a major pi update can break it — the rail disappears or jumps inaccurately. The documented response is to uninstall with pi remove npm:pi-conversation-outline.
## References
## Related entries
$ pi-open-tui
Polished terminal interface for pi: model/thinking header, runtime-aware footer, framed editor, turn metrics (TPS / TTFT / stalls / cost), and 50+ runtime detectors — all configurable from /open-tui.
$ pi-reverse
Fullscreen TUI extension that pins pi's input at the top and stacks Q&A pairs newest-first, question in view.
$ pi-statusline
Compact TUI statusline: model and thinking on the border, token flow and context usage in the footer.
## Guides
Last updated: Sep 18, 2026