Appearance
XTPOPSGR — pop SGR stack (CSI # })
ESC [ # }XTPOPSGR restores the SGR (Select Graphic Rendition) state most recently pushed by XTPUSHSGR (
CSI # {). The sequence is CSI # }. Always paired with a matching push earlier in the same session — pops without a corresponding push are no-ops on most terminals.
This sequence is the second half of the SGR push/pop pattern that lets TUI code temporarily change attributes without permanently affecting the caller's state. Library authors can wrap subroutines in CSI # { ... CSI # } and trust that the caller's bold/color/underline state survives unchanged. Adopted by xterm, Ghostty, foot, Contour, and others.How this is testedautomated
Send
Send
\x1b[#{ followed by \x1b[#}, verify the sequences are consumed and the terminal stays responsive.The same probe runs against headless backends (via Termless) and real terminal apps (via a daemon launched in each terminal). This lets us distinguish parser correctness from rendering correctness.
Analysis2026-04-06
Supported by 9 of 14 backends (64%)
Terminal Applications
| Terminal | Version | Support | Notes |
|---|---|---|---|
| iTerm2 | 3.6.9 | ✓ yes | Sequence consumed; terminal responsive |
| Ghostty | 1.3.1 | ✓ yes | Sequence consumed; terminal responsive |
| Terminal.app | 2.15 | ✓ yes | Sequence consumed; terminal responsive |
| Kitty | 0.46.2 | ✓ yes | SGR stack not exposed via Python batch bridge |
| VS Code | 1.113.0 | ? unknown | |
| Warp | 0.2026.03.18.08.24.03 | ? unknown | |
| Cursor | 2.6.21 | ? unknown |
Headless Backends
Parser correctness only — a ✓ means the parser accepts the sequence.
| Backend | Version | Support | Notes |
|---|---|---|---|
| vt100.js | 0.2.1 | ✓ yes | |
| vterm | 0.2.0 | ✓ yes | |
| xterm.js | 5.5.0 | ✓ yes | |
| WezTerm | 0.1.0-fork.5 | ~ partial | SGR stack not exposed in headless mode; sequence consumed silently |
| Alacritty | 0.26.0 | ✗ no | SGR stack not implemented by alacritty |