Appearance
VS Code Shell Integration (OSC 633)
ESC ] 633 ; A BELOSC 633 is VS Code's shell integration protocol, extending OSC 133 with additional markers for command detection, output boundaries, and shell state. It enables features like command decorations (green/red markers showing success/failure), run-recent-command, and sticky scroll for terminal output.
The protocol uses escape sequences to mark four boundaries: prompt start (A), command start (B), command executed (C), and command finished (D, with exit code). VS Code's built-in shell integration scripts for bash, zsh, fish, and PowerShell emit these markers automatically. The terminal then knows exactly where each prompt, command, and output block begins and ends.
OSC 633 adds VS Code-specific extensions beyond OSC 133: property reporting (P;key=value) for shell state like current directory and shell type, command line reporting (E) for the exact command text, and continuation prompt marking for multi-line commands. Other terminals (Kitty, WezTerm) support the base OSC 133 protocol but not the VS Code-specific extensions.
How this is tested: Send
OSC 633 ; A BEL (VS Code prompt start marker) and verify the terminal accepts the sequence. OSC 633 is a superset of OSC 133.Analysis2026-03-26
Supported by 7 of 8 terminals (88%). Not supported by: Cursor. Part of the Rich TUI baseline.
Supported by 11 of 13 backends (85%)
Terminal Applications
| Terminal | Version | Support | Notes |
|---|---|---|---|
| iTerm2 | 3.6.9 | ✓ yes | |
| Ghostty | 1.3.1 | ✓ yes | |
| VS Code | 1.112.0 | ✓ yes | |
| Warp | 0.2026.03.18.08.24.03 | ✓ yes | |
| Cursor | 2.6.21 | ✓ yes | |
| tmux | 3.6a | ✓ yes | |
| Kitty | 0.46.2 | ✓ yes | VS Code shell integration (OSC 633) not supported |
| Terminal.app | 2.15 | ✓ yes | |
| GNU Screen | 5.0.1 | ✓ yes |