Blog · September 23, 2026 · 9 min read · by Vilva Athiban P B

Claude Code Notifications on WSL and Windows

If you run Claude Code inside WSL on Windows, you have probably noticed that every notification guide on the internet quietly assumes you are on a Mac. You set up the hook, Claude finishes a task, and — nothing. No sound, no toast, no taskbar flash. You go back to staring at the terminal, which is the exact thing you were trying to stop doing.

This is not you misconfiguring something. WSL is a genuinely awkward environment for notifications, for reasons worth understanding before you start pasting config. Here is what actually breaks, and the three approaches that work.

Why WSL notifications fail in the first place

There are three separate failure points, and most people hit at least two of them.

The terminal bell usually goes nowhere. The classic cross-platform trick is to echo the ASCII bell character — echo -e "\a" — and let the terminal turn it into a sound. In WSL this frequently produces silence. The bell has to survive the trip from the Linux process, through the terminal emulator, to a Windows sound device, and any link in that chain can swallow it.

Linux notification tools do not cross the boundary. The obvious Linux answer is notify-send. Under WSL2 it does not reach Windows: there is no desktop notification daemon on the Windows side listening for it. You can install it, run it, get exit code zero, and see nothing at all. This is the single most common dead end.

Windows Terminal has toasts, but Claude Code does not use them. Windows Terminal supports progress indicators and toast notifications natively. Claude Code running inside WSL does not emit the sequences that trigger them, so the capability sits there unused.

The consequence is that you cannot fix this from the Linux side alone. Something has to deliberately call out to Windows.

The mechanism: hooks plus Windows interop

Claude Code fires hooks on specific events, configured in ~/.claude/settings.json. The two that matter here are Stop, which fires when Claude finishes a response and is waiting for you, and Notification, which fires when Claude needs approval or input mid-task. Hooks receive JSON context on stdin, so a script can read what happened and react to it.

The WSL-specific part is that your hook command needs to invoke powershell.exe rather than a Linux notification tool. WSL interop lets a Linux process launch Windows executables directly, as long as powershell.exe is reachable on your PATH. That single detail is what makes the whole thing work, and checking it is the first thing to do when a setup silently fails:

which powershell.exe

No output means interop is off or PowerShell is not on your path, and nothing below will work until that is fixed. If you have never set up hooks before, our guide to Claude Code hooks covers the general structure first.

Option 1: a sound, in one line

If all you want is an audible ping, this is the lowest-effort thing that reliably works. It calls into Windows and plays a system sound, with no modules to install:

powershell.exe -c "[console]::beep(800,300)"

Wire that as the command for a Stop hook and you are done. It is crude, it carries no information about what happened, and it will not help if your headphones are off — but it takes two minutes and it removes the need to keep glancing at the terminal.

Option 2: real Windows toast notifications

A toast is better than a beep because it survives you looking away and tells you which project finished. The common route is the BurntToast PowerShell module. In a Windows PowerShell session, not inside WSL:

Set-ExecutionPolicy -Scope CurrentUser RemoteSigned
Install-Module BurntToast -Scope CurrentUser -Force

Then your hook command shells out through interop to raise a toast with a title and message. Because hooks receive JSON on stdin, you can parse out the session or project name first and put it in the toast body, which matters a lot once you are running more than one Claude Code session at a time and a bare "done" tells you nothing useful.

Two practical warnings. Windows Focus Assist will suppress toasts without telling you, so check it before concluding your script is broken. And quoting is genuinely painful here: you are nesting a PowerShell string inside a shell string inside JSON, and a single mis-escaped quote fails silently. Put the logic in a small .sh file and point the hook at the file rather than inlining it.

Option 3: skip the desktop entirely

Worth saying plainly, because the WSL toast rabbit hole can eat an afternoon: a desktop notification only helps if you are at the desktop. The whole reason people want Claude Code notifications is usually that they have gone to make coffee, moved to a meeting, or started doing something else while a long task runs.

If that is your situation, routing the notification off the machine is both more useful and considerably easier to configure — there is no interop layer, no execution policy, and no Focus Assist to fight. Phone notifications for Claude Code covers that path, and the same Stop and Notification hooks drive it.

The honest trade-off: a toast is instant and free, and it is the right answer if you mostly stay at your desk and just want to stop context-switching every ninety seconds. Push to a phone wins the moment you leave the room.

A debugging order that saves time

When nothing appears, work through these in order rather than changing several things at once.

  1. Run which powershell.exe. No path, no notifications.
  2. Run your notification command by hand in the WSL shell. If it does not fire when you run it directly, the problem is not Claude Code.
  3. Check Windows Focus Assist and the notification settings for the terminal app you are using.
  4. Confirm the hook is actually firing at all — have it write a line to a log file as well as raising the toast.
  5. Check whether you have settings in both the project .claude/settings.json and your home directory. Precedence surprises are a common cause, and our notifications-not-working guide covers the non-WSL versions of the same problem.

The short version

WSL notifications fail because the Linux side has no way to reach the Windows notification system on its own. The fix is always the same shape: a Claude Code hook that calls powershell.exe through WSL interop. A beep takes two minutes, a BurntToast toast takes about twenty, and if you are not at the desk anyway, sending it to your phone is less work than either.

Keep reading

Desk Exercises for Programmers: 15 Moves to Do While Your AI Agent Codes

7 min read

Exercise While Coding: Turn Claude Code Wait Time Into Micro-Workouts

7 min read

Claude Code Notch Notifications on Mac: See When Claude Is Done Without Watching the Terminal

7 min read

Claude Code Tips and Tricks: 12 Ways to Use Claude Code Effectively

8 min read

Claude Code Multiple Sessions: How to Run Agents in Parallel Without Losing Track

6 min read

A Claude Code Workflow That Doesn't Involve Watching the Terminal

5 min read

Claude Code Hooks: A Practical Guide to Automating Your Agent Workflow

7 min read

Claude Code Auto Mode: Fewer Permission Prompts Without Living Dangerously

7 min read

Claude Code Subagents: How to Delegate Work to Specialized Agents

7 min read

Claude Code Context Management: Treat the Context Window Like a Budget

6 min read

Per-Subagent Model Selection: Route the Grunt Work Down, Keep the Judgment Up Top

7 min read

Skills and Plugins: How to Teach Claude Code Your Way of Working

7 min read

Claude Code Background Tasks: Run Long Commands Without Blocking Your Session

6 min read

Codex CLI Notifications: How to Get a Ding When Codex Is Done or Needs Input

7 min read

Cursor Notification When Done: Every Way to Get Notified When Cursor Finishes

6 min read

Claude Code Notifications: How to Get Notified When Claude Code Finishes or Needs Your Input

6 min read

Want to Be Notified When Claude Responds? How Claude Notifications Work on Web, Desktop, and Mobile

5 min read

Claude Code Notification Scripts: Copy-Paste Recipes for Every Platform

6 min read

Get a Ding the Moment Codex Needs Your Response

6 min read

Get Notified the Moment Claude Code Is Waiting for Your Input

6 min read

“Notifications Are Turned Off for Claude” — Here Is the Fix

6 min read

Codex Sound When Done: Make Codex CLI Play a Sound When It Finishes

6 min read

terminal-notifier + Claude Code: Native macOS Alerts When Your Agent Finishes

6 min read

Gemini CLI Notifications: How to Get a Sound or Alert When Gemini Finishes

6 min read

Get Claude Code Notifications on Your Phone

6 min read

Claude Code Remote Control, Explained

7 min read

preferredNotifChannel: Claude Code's Built-In Notification Setting

6 min read

Claude Code Notifications in tmux and Over SSH

7 min read

Claude Code Effort Levels: Why Your Setting Keeps Getting Ignored

8 min read

Codex vs Claude Code Notifications: How Each One Tells You It Is Done

8 min read

Claude Code Notifications Not Working: A Diagnostic Checklist

10 min read

Claude Code Notifications Inside Your Editor's Terminal

7 min read

CLAUDE_CODE_DISABLE_BACKGROUND_TASKS Explained

7 min read

CLAUDE_CODE_DISABLE_BG_SHELL_PRESSURE_REAP Explained

8 min read

Cursor Alerts Explained: Every Alert Cursor Raises, and How to Control Them

7 min read

Claude Code Environment Variables: The Groups That Actually Matter

10 min read

Claude Code Checkpoints and /rewind

8 min read

Claude Remote Control: How It Works, Turning It Off, and Auto Mode

7 min read

Claude Code /loop: Poll a Deploy, Babysit a PR, and Get Told When It's Done

8 min read

Setting Up NotchFit With OpenAI Codex CLI: Hooks, $notchfit-plan, and the Daily Flow

7 min read

Claude Mods Explained: What the New Plugin Layer Can Do, and How to Turn On 'You Should Know'

9 min read

NotchFit vs Mac Break Reminder Apps: A Clock or a Signal From Your Coding Agent?

8 min read

Claude Code Headless Mode: Running claude -p in Scripts and CI, and the Three Signals That It Finished

10 min read

Building a Movement Habit at a Desk: Use the Agent Run as the Cue, One Set as the Unit, and Streaks Carefully

8 min read

Claude Code MCP Servers Explained: Adding Servers, Choosing a Scope, Handling Secrets, and Why Long Tool Calls Go to the Background

10 min read

/notchfit:plan Explained: How Claude Code or Codex Writes a Weekly Workout Plan the Notch Can Actually Run

8 min read

Claude Code Spinner Verbs Explained: What “Pondering” and “Brewing” Mean, How to Change Them, and Why You Should Stop Watching the Spinner

7 min read

Why NotchFit's Done and Permission Alerts Wait Until Your Set Ends, When That Costs You, and How to Turn the Workout Off

7 min read

How to Resume a Claude Code Session: --continue vs --resume, Naming Sessions, the Session Picker, Branching, and What Comes Back

9 min read

NotchFit on a Mac Without a Notch: How Pill Mode Works on Mac mini, iMac, Mac Studio and a MacBook With the Lid Closed

6 min read

How to Run a Claude Code Session in the Background: /background, claude --bg, Agent View, and Getting Back to It

9 min read

What a Notch App Can See: NotchFit's Local-First Design, What the Claude Code and Codex Hooks Send, and What Stays on Your Mac

7 min read

Why Codex CLI Asks for Permission Every Time, and How to Tune the Sandbox and Approval Policy Without Going Full Access

8 min read

What to Do While Claude Code or Codex Works: A Simple Protocol for the Two-to-Twenty-Minute Gap in Every Agent Run

7 min read

Is It Possible to Get a Notification When Claude Code or Codex Hits a Reset? Yes for Claude Code: the quota_auto_resume Hooks, Explained

8 min read

What a MacBook Notch App Can Actually Do: The Five Kinds of Notch Utility, Their Trade-offs, and Where NotchFit Fits

7 min read

How to Make MCP Servers Not Take Up as Much Context in Claude Code: Tool Search, alwaysLoad, Scopes and Output Caps

8 min read

The notchfit Command Line: Drive Your Workout, Read Status as JSON, Validate Plans and Test the Notch Without Leaving the Terminal

7 min read

How to Audit MCP Tool Calls Made by Claude Code: A Five-Minute Hook Audit Log, OpenTelemetry Tool Events, and the Transcript for Investigations

9 min read

Exercise Snacks: What the Research Actually Says About One-Minute Vigorous Breaks, What It Does Not, and How NotchFit's Agent-Run Sets Compare

8 min read

How Long Until a Claude Code MCP Tool Call Times Out? The Four Timers (Startup, Two-Minute Backgrounding, Idle, Wall-Clock), Their Defaults, and Which One to Change

8 min read

Sitting Too Long as a Developer: The Posture Problems Coding Agents Made Worse, What the Research Says About Breaking Up Sitting, and How NotchFit Turns an Agent Run Into the Break

8 min read

Claude Code .mcp.json Explained: Where Project-Scoped MCP Servers Are Read From, What Happens in Subfolders and Monorepos, and Why a Committed Server Shows Pending Approval

8 min read

Standing Desk Exercises for Developers: Why Standing Still Is Not the Goal, Eight Movements That Fit a Thirty-Second Agent Run, and How NotchFit Cues Them From the Notch

8 min read

The claude mcp Command Reference: add Syntax by Transport, What --scope local, project and user Actually Mean, add-json and add-from-claude-desktop, list, get, remove, login and serve

9 min read

Your First Week With NotchFit: Install and Simulate, Run Real Tasks, Write a Smaller Plan Than You Want, Tune the Alerts, Survive the First Skipped Day, and Decide What Stays

8 min read

How to Stop a Running Claude Code Task: Esc vs Ctrl+C, Background Tasks, Subagents, and Disconnecting Remote Control

8 min read

Pomodoro vs Agent-Driven Breaks: Timing Movement to Claude Code and Codex Runs Instead of a Timer

7 min read

Claude Desktop MCP Configuration: claude_desktop_config.json, Logs, Extensions, and the Difference From Claude Code

9 min read

The 20-20-20 Rule for Developers: Eye Strain, the Evidence, and Agent Runs as the Cue

8 min read

Claude Agent SDK + MCP Servers: mcpServers, allowedTools, Status Checks and Auth

9 min read

Discreet Desk Exercises for an Open-Plan Office While Claude Code Runs

7 min read

claude remote-control Server Mode: Run Claude Code as a Session Server

9 min read

Wrist and Forearm Stretches for Developers: A 60-Second Routine for Every Claude Code Run

7 min read

Claude Remote Control vs Claude Code on the Web: Which to Use and How They Differ

9 min read

Neck and Shoulder Stretches for Developers: A 90-Second Routine Between Agent Runs

7 min read

What Happens When You Step Away From a Claude Code Session: Prompt Cache Expiry, Idle Compaction, and When to Come Back

8 min read

Hip Flexor and Lower Back Stretches for Developers: A Two-Minute Standing Routine Between Agent Runs

7 min read

Claude Code's Monitor Tool: Watch Logs, CI Runs and PRs (Even a WebSocket) and Let Claude React While You Keep Working

7 min read

Hunched Over the Keyboard? Upper-Back (Thoracic) Stretches for Developers: A Two-Minute Seated Routine Between Agent Runs

6 min read

Claude Code Ultrareview: The 15–25 Minute Cloud Review, What to Do While It Runs, and How the Findings Come Back

8 min read

Why Your Legs Go Dead After a Long Claude Code Session: A Two-Minute Standing Calf, Glute and Hamstring Routine Between Agent Runs

7 min read

claude --teleport: Pull a Cloud Session Into Your Terminal, Start One With --cloud, Send Follow-Ups From the CLI, and the Requirements That Trip People Up

8 min read

Rounded Shoulders From Typing? A Two-Minute Chest Opener, Chair Twist and Wall Press Desk Routine for Developers Between Agent Runs

7 min read

Claude Code ultrathink Explained: It Now Runs the Turn at xhigh Effort, How It Differs From /effort, What It Costs in Time, and What to Do While It Runs

7 min read

Best Break Reminder Apps for Mac in 2026: Time Out, Stretchly, BreakTimer, LookAway and NotchFit Compared

7 min read

Claude Code 2.1.319: denyInsteadOfPrompting, MCP Background Tasks and What Changes for Unattended Runs and Notifications

8 min read

Drink Water and Stand Up Cues for Developers: Use Claude Code Agent Runs as Hydration and Standing Reminders

7 min read

Claude Code 2.1.323: Code Mode, Progress Heartbeat, Auto-Mode Fallback and 1M Context — What Changed for Unattended Runs

9 min read

Notch Media Controls on a Mac: What the MacBook Notch Can and Cannot Do, Dynamic Island-Style Apps vs NotchFit

7 min read