wispterm-notify-setup

WispTerm Notify Setup

Overview

Install a small notifier that makes Claude Code and Codex surface a WispTerm notification (OSC 777 toast + terminal bell badge) when a turn finishes or a confirmation is needed. The notifier is agent-agnostic and the installers are idempotent — safe to re-run.

Workflow

1. Determine the target from the user's words and WispTerm state.

   • If the user names an existing WispTerm tab/server/profile (for example CPU3), call terminal_list first and match by title/kind.
   • If a saved SSH profile is named but no SSH tab is already open, call ssh_profile_connect {"profile_name":"<name>"} and use the returned surface_id.
   • Never ask the user to re-provide SSH host/user/port/password when the target is an existing saved WispTerm profile. Ask only if the profile is missing or authentication fails.

2. Install using the target-specific transfer path.

   • Local POSIX / macOS / WSL: copy the bundled POSIX scripts directly to the target shell, then run:

     sh ./install-wispterm-notify.sh
     

     When targeting an already-open WSL surface, use wsl_session_exec to run commands in that surface. Do not use scp for WSL.

   • Local Windows PowerShell: copy the bundled PowerShell scripts directly to the Windows profile and run install-wispterm-notify.ps1 with powershell_exec:

     powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\install-wispterm-notify.ps1
     

   • Remote saved SSH profile: use scp, not pasted heredocs, to transfer the bundled POSIX scripts to the remote server, then run the POSIX installer in that SSH session. From Windows/WispTerm, prefer the bundled profile-aware helper because it reads %APPDATA%\wispterm\ssh_hosts, decodes the saved profile, supports saved-password profiles via SSH_ASKPASS, and uses scp.exe/ssh.exe without connection sharing:

     powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\install-wispterm-notify-remote.ps1 -ProfileName "CPU3"