Skip to content

OSC 133;C command executed (FTCS_COMMAND_EXECUTED)

Category: extensions · Baseline: rich · Tags: Operating System Commands (OSC) · Specification ↗

ESC ] 133 ; C BEL

OSC 133;C (also known as FTCS_COMMAND_EXECUTED) marks the transition from the command line to command output. Shells emit this immediately after the user presses Enter and before the command begins producing output. It tells the terminal: everything from here until 133;D is the command's output.

This marker lets the terminal group output blocks for selection, scrolling, and folding. Features like "copy command output" and "scroll by command" depend on knowing where output begins. Combined with 133;D, it enables the terminal to compute command duration and show success/failure decorations.

How this is testedpartial
Send OSC 133 ; C BEL and verify the terminal consumes the sequence (cursor doesn't advance, terminal remains 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 all 9 tested terminals — universal adoption. Part of the Rich TUI baseline.

Supported by 11 of 14 backends (79%)

Terminal Applications

TerminalVersionSupportNotes
iTerm23.6.9✓ yes
Ghostty1.3.1✓ yes
Terminal.app2.15✓ yes
Kitty0.46.2✓ yes
VS Code1.113.0? unknown
Warp0.2026.03.18.08.24.03? unknown
Cursor2.6.21? unknown

Headless Backends

Parser correctness only — a means the parser accepts the sequence.

BackendVersionSupportNotes
Alacritty0.26.0✓ yes
vt100.js0.2.1✓ yes
vterm0.2.0✓ yes
WezTerm0.1.0-fork.5✓ yes
xterm.js5.5.0✓ yes