Features›Modes›Pop color palette (CSI # Q)

Pop color palette (CSI # Q)

Category: modes · Baseline: rich · Tags: Xterm Extensions · Specification ↗

ESC [ # Q

XTPOPCOLORS restores the color palette most recently pushed by XTPUSHCOLORS (CSI # P). The sequence is CSI # Q. Always paired with a matching push earlier in the session — pops without a corresponding push are no-ops on most terminals. Used by TUI applications that install a custom palette during their run and want to restore the user's theme on exit. The push/pop pattern avoids needing to query every palette slot via OSC 4 ; n ; ? and write each one back manually. Adopted by xterm (patch #357), Ghostty, foot, Contour, and other modern terminals.

How this is testedautomated
Send \x1b[#P followed by \x1b[#Q, 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 8 of 9 terminals (89%). Not supported by: Alacritty. Part of the Rich TUI baseline. Notes: Alacritty: Color palette stack not implemented by alacritty.

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	Color palette 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	Color palette stack not exposed in headless mode
Alacritty	0.26.0	✗ no	Color palette stack not implemented by alacritty

← Back to matrix · modes features