If you keep your agent in VS Code's integrated terminal, the notification banner
never arrived — and not because VS Code refused it. We were never sending one:
that terminal isn't among the hosts the plugin recognises, so the sequence was
skipped entirely, extension or no extension.
VS Code has no desktop notification of its own for these sequences and discards
them without printing anything, which is why nothing ever looked broken. But the
notifier extensions people install for exactly that gap read the same
OSC 777;notify form Warp and Ghostty do — and now they receive it. With no
extension installed nothing is shown and nothing is printed; the line, the chime
and the status line work as they always did. Cursor and other VS Code forks are
covered by the same check.
Found by a tester running Claude Code inside VS Code, a host this plugin had
never been tried in. Terminals that aren't recognised still get no sequence at
all — stray bytes in someone else's session are worse than a missing banner, and
that path now has a test of its own.