Add option to suppress SessionStart message in non-Warp terminals#4
Open
RonAmihai wants to merge 1 commit intowarpdotdev:mainfrom
Open
Add option to suppress SessionStart message in non-Warp terminals#4RonAmihai wants to merge 1 commit intowarpdotdev:mainfrom
RonAmihai wants to merge 1 commit intowarpdotdev:mainfrom
Conversation
…essage 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 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The SessionStart hook displays an "ℹ️ Warp plugin installed but you're not running in Warp terminal" message every time Claude Code starts in a non-Warp terminal.
However, the plugin's notifications (OSC 777) work in any terminal that supports OSC 777 — not just Warp. For example, Ghostty fully supports OSC 777, and the plugin's Stop and Notification hooks work correctly there. The message is misleading for these users and clutters the session start output.
Solution
Add a
CLAUDE_CODE_WARP_QUIET_SESSION_START=1environment variable check that suppresses the message when set. This gives users who intentionally run the plugin in non-Warp terminals a clean way to opt out of the banner without modifying the plugin.Usage
The default behavior is unchanged — users who don't set the variable see the same messages as before.