Back to home

baobaolaodie

cc-notifier

Windows desktop notifications for Claude Code and DeepSeek Harness sessions. Click any toast to restore the session window — unlike similar tools that only notify without focus actions. Zero external npm dependencies.

Stars
0
Language
JavaScript
Created
Aug 13, 2026
Updated
Aug 16, 2026

Introduction

cc-notifier

Windows desktop notifications for Claude Code and DeepSeek Harness sessions
Permission requests · Questions · Tool errors · Waiting for input · Click-to-return

Quick Start License

version 0.1.0 Claude Code DeepSeek Harness Windows 10/11 Node.js 18+ Python 3

English · 中文

cc-notifier raises a native Windows toast with sound when an agent needs your attention and you are not looking at its window. It serves Claude Code through its hook system and DeepSeek Harness through a small bundle plugin, sharing one daemon pipeline. Clicking a toast returns you to the session window. Zero third-party npm dependencies.

Features

FeatureDescription
Interruption eventsNotifies on permission requests, questions, tool errors, and waiting for input
Focus awarenessSuppresses notifications while the session window is focused; notifies only when it is not
Click-to-returnSetForegroundWindow targets the session window; browser tabs activate via UIA
Multi-sessionEach session binds its own window handle; toasts carry the session identity
Localized notificationsToast text follows the Windows display language (auto) or a language setting (zh/en)
DeepSeek HarnessThe dsh-notifier plugin covers web and tui profiles with one install

Quick Start

Prerequisites

  • Windows 10 or 11
  • Node.js 18 or later
  • Python 3 with the winrt packages: pip install winrt-runtime winrt-Windows.UI.Notifications winrt-Windows.Data.Xml.Dom

Install (Claude Code)

node scripts/install.mjs

The installer backs up ~/.claude/settings.json, injects six hooks, registers the cc-notifier AppUserModelID, and writes the default config. Open a new Claude Code session afterwards.

Install (DeepSeek Harness)

# from the repository root; relative paths only
dsh plugin --profile web add ./plugins/dsh-notifier
dsh plugin --profile dsh-tui add ./plugins/dsh-notifier

Verified against dsh 0.1.0-rc.6 on Windows 11 (2026-08-16): web and tui profiles, all four notification types, focus-aware silence, click-to-return, and the tarball install flow.

Verify

npm test

Usage

Claude Code

Start a session and switch away. The system notifies when Claude requests a permission, asks a question, finishes a turn, or hits a tool error:

claude
# switch to another window; toasts appear when Claude needs you

DeepSeek Harness

The plugin forwards dsh session events into the same pipeline. Web sessions bind to the browser window; tui sessions bind to the terminal window:

dsh web          # or: dsh --profile web
dsh-tui          # or: dsh --profile dsh-tui

Manual trigger (testing)

node scripts/test.mjs permission-request   # permission-request | ask-user-question | tool-result | stop | session-start

Toasts are suppressed while the target window is focused, so switch away to observe them.

Configuration

Edit ~/.cc-notifier/config.json (created on install):

KeyDefaultDescription
enabledtrueSet to false to disable notifications globally
dedupWindowMs0Deduplication window (ms); 0 = no dedup; >0 merges per session+type
pythonPathemptyAbsolute path of the toast interpreter (written by the installer); empty = python from PATH
pollIntervalMs10000Daemon window-poll period (ms)
windowWhitelist[]Browser process whitelist for dsh web binding/focus (e.g. chrome.exe/msedge.exe)
soundtrueSet to false to mute toast sound
languageautoToast language: auto (system display language, zh-*→zh, en-*→en, other/failure→en), zh, or en

Architecture

An event-driven pipeline runs only while sessions are active. Claude Code hooks and the dsh plugin both produce the same normalized payloads; a resident daemon decides whether to notify, and a Python agent shows the toast:

%%{init: {'theme': 'base', 'themeVariables': {'fontSize': '14px'}}}%%
flowchart LR
    CC["Claude Code<br/>hooks"] --> NA["notify-agent.mjs<br/>forwarder"]
    DSH["dsh-notifier<br/>plugin · web/tui"] --> NA
    NA -->|"HTTP · localhost"| DM["daemon.mjs<br/>sessions · focus · lifecycle"]
    DM --> TA["toast-agent.py<br/>winrt toast"]
    TA -->|"click"| WIN["session window<br/>SetForegroundWindow · UIA tab"]
    DM --> ST[("state · logs<br/>%LOCALAPPDATA%")]

    classDef client fill:#3B82F6,stroke:#2563EB,color:#fff,stroke-width:2px
    classDef service fill:#10B981,stroke:#059669,color:#fff,stroke-width:2px
    classDef data fill:#8B5CF6,stroke:#7C3AED,color:#fff,stroke-width:2px

    class CC,DSH,WIN client
    class NA,DM,TA service
    class ST data

The daemon is single-instance: it wakes on demand, exits after 60 seconds of no sessions, and self-restarts when its code changes. Sessions re-register automatically after a daemon restart.

Project Structure

├── scripts/               # Runtime pipeline
│   ├── notify-agent.mjs   # Hook forwarder (Claude Code)
│   ├── daemon.mjs         # Resident process: sessions, focus, dedup
│   ├── toast-agent.py     # Python winrt toast + click handling
│   └── lib/               # Shared modules, win32 bridge, UIA helpers
├── plugins/
│   └── dsh-notifier/      # dsh bundle plugin (web + tui profiles)
├── test/                  # node:test suite (explicit file list)
├── docs/                  # Installation, usage, troubleshooting (bilingual)
└── package.json           # Zero runtime dependencies

Tech Stack

LayerTechnologyPurpose
RuntimeNode.js 18+ (ESM)Forwarder, daemon, plugin
NotificationsPython 3 + winrtWindows toast rendering and activation
Window bridgePowerShell 5.1 + C# helpersWindow enumeration, foreground query, UIA tab activation
Testingnode:testUnit + integration tests

Deployment

CI runs on GitHub Actions (test × 6 matrix across Node 18/20/22 on Ubuntu and Windows, plus quality, pr-policy, docs-links, and a summary job). See .github/workflows/ci.yml.

Contributing

  1. Fork the repository
  2. Create a feature branch (git checkout -b feature/your-change)
  3. Commit with Conventional Commits (feat:, fix:, docs:, …)
  4. Open a Pull Request

PRs must pass the full CI suite, including the bilingual documentation mirror check and version consistency checks. See CONTRIBUTING.md.

License

MIT