From 82de01003a34bc3a6f2f2871a32f29f19340fd48 Mon Sep 17 00:00:00 2001 From: Ron Amihai Date: Mon, 23 Feb 2026 14:01:40 +0200 Subject: [PATCH] Add CLAUDE_CODE_WARP_QUIET_SESSION_START option to suppress startup message The SessionStart hook shows a "not running in Warp terminal" message in non-Warp terminals. However, other terminals like Ghostty also support OSC 777 notifications, so the plugin works fine there and the message is misleading. Setting CLAUDE_CODE_WARP_QUIET_SESSION_START=1 suppresses the message for users who intentionally run the plugin in non-Warp terminals. Co-Authored-By: Claude Opus 4.6 --- plugins/warp/scripts/on-session-start.sh | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/plugins/warp/scripts/on-session-start.sh b/plugins/warp/scripts/on-session-start.sh index 4d5e7fb..6b23f87 100755 --- a/plugins/warp/scripts/on-session-start.sh +++ b/plugins/warp/scripts/on-session-start.sh @@ -1,6 +1,13 @@ #!/bin/bash # Hook script for Claude Code SessionStart event # Shows welcome message and Warp detection status +# +# Set CLAUDE_CODE_WARP_QUIET_SESSION_START=1 to suppress this message. +# Useful when running in non-Warp terminals that support OSC 777 +# notifications (e.g. Ghostty), where the plugin works but the +# "not running in Warp" message is misleading. + +[ "$CLAUDE_CODE_WARP_QUIET_SESSION_START" = "1" ] && exit 0 # Check if running in Warp terminal if [ "$TERM_PROGRAM" = "WarpTerminal" ]; then