dsh-thinking-notifier
DeepSeek Harness 桌面弹窗插件：在右下角的置顶卡片中显示 AI 思考状态，并在 AI 请求权限、等待您选择或完成思考时提醒您
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:6-debug-6/dsh-thinking-notifier#7f12b7411bc660906bfdae0f5294175724ea785aThinking Notifier 以 dsh-thinking-notifier 发布，当前版本为 1.3.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
点击下方 Badge 复制 Markdown，粘贴到 README 即可。
验证 package.json 声明的 GitHub 仓库，即可管理这个公开页面。认领后，Hub 会优先安排当前版本的安全扫描，并在通过后公开展示结果。
认领这个 Plugin →A DeepSeek Harness (DSH) plugin that shows a small always-on-top desktop popup in the bottom-right corner of your screen. It mirrors the AI's thinking status in real time and alerts you when the AI requests permission, waits for a choice from you, or finishes thinking — even when you are working in other apps, browsers, or virtual desktops.
中文说明见 README.zh.md
| State | Popup | Sound |
|---|---|---|
| AI is thinking | DeepSeek-blue pulsing dot + AI 正在思考… + elapsed time. Auto-collapses to a 25 px slim right-edge tab after 5 s; hover or click the tab to expand it again | none |
| AI waits for your choice | Violet pulsing dot + AI 正在等待你的选择 + the question heading, the first question's option labels (选项：A / B, （可多选） for multi-select, （共 N 问） when several questions arrive at once) and how long it has been waiting. Stays expanded until you answer | system Question |
| AI requests permission | Amber pulsing dot + AI 请求权限 + session/tool name. Stays expanded until you decide | system Exclamation |
| AI finished thinking | Green dot + AI 已完成思考, auto-hides after 12 s | system Asterisk |
| Idle | Hidden | none |
#1E2235 / #4D6BFE).DSH process
└─ lib/index.js (host plugin)
├─ listens to session/event: turn/start, turn/end, approval/asked, approval/decided, session/title
├─ rebuilds existing session state from ctx.sessions.list() at startup
│ (a session whose log ends inside an open turn is treated as not running)
├─ wraps ctx.userQuestions.ask to observe ask_user_question
│ (that state produces no session event, and a second UI provider cannot be registered)
├─ serves a local status JSON at http://127.0.0.1:7389/status
└─ launches the desktop popup process
├─ Windows: desktop-popup.ps1 (PowerShell + WPF)
└─ macOS/Linux: desktop-popup.py (Python 3 + tkinter)
Desktop popup
├─ polls /status every second
├─ renders the DeepSeek-style card (question/pending/running/done/idle)
├─ plays a system sound on question/pending/done transitions
├─ auto-collapses to the right edge while running; stays expanded while waiting for you
└─ hides while idle, keeps running in the background
GET http://127.0.0.1:7389/status returns:
{
"ok": true,
"mode": "question",
"statusText": "AI 正在等待你的选择",
"sessionText": "Choose Mode",
"detailText": "选项：样式 A / 样式 B（可多选）",
"timeText": "已等待 00:12",
"pendingKind": "question",
"pendingTool": null,
"runningSince": null,
"doneAt": null,
"questionCount": 1,
"questionSince": 1791374946369,
"appUrl": "http://127.0.0.1:3080",
"now": 1791374946369
}
mode priority: pending (an approval is waiting) > question (a question is waiting) > running > done (shown for 12 s) > idle.
pendingKind is approval or question. timeText is the thinking timer while running and the waiting time while question; detailText carries the first question's options.
cd dsh-thinking-notifier
dsh plugin --profile web add .
# Restart DSH web so the host plugin is loaded
dsh web
dsh plugin --profile web add dsh-thinking-notifier
dsh web
dsh plugin --profile web remove dsh-thinking-notifier
| Environment variable | Default | Description |
|---|---|---|
DSH_THINKING_NOTIFIER_PORT | 7389 | Local status server port. If busy, the next 10 ports are tried. |
DSH_THINKING_NOTIFIER_NO_POPUP | unset | Set to 1 to run the status server without launching the desktop popup (headless, tests). |
dsh web)^22.19.0 || >=24.0.0tkinterBeing explicit about what has actually been tested, so nobody is surprised:
| Area | Status |
|---|---|
| Thinking / done states, popup geometry, sounds, single instance | verified on Windows 10/11 (PowerShell 5.1 + WPF) |
Question state (ask_user_question) | verified end to end in a live DSH session (a real question drove the popup into the waiting state, and it cleared when the answer arrived), against the real ctx.userQuestions service in a cordis context, and by the smoke test |
| Permission alert (amber) | verified only with the mock status service. On a Windows DSH install without a confining sandbox, an out-of-workspace write is not intercepted, so no approval is raised by the runtime; the request only appears when a tool call explicitly asks for a sandbox_permissions escalation or a pre-execute hook returns ask |
desktop-popup.py (macOS/Linux) | never run on real hardware — syntax-checked only |
Popup process stacking after repeated dsh web restarts | the launcher kills stale popups for its own port before starting a new one; verified for a single restart cycle |
# status-machine smoke test (fake cordis context, no popup, port 17389)
npm test
# render the popup against a mock status service, on a spare port
node tools/mock-status.mjs question --port 17389
powershell -NoProfile -ExecutionPolicy Bypass -File desktop-popup.ps1 -Port 17389 # Windows
python3 desktop-popup.py --port 17389 # macOS/Linux
Use a spare port for popup experiments: the real popup on 7389 is left alone, because the plugin only cleans up popup processes belonging to its own port.
dsh-thinking-notifier/
├── lib/
│ └── index.js # host plugin: state machine + status service + popup launcher
├── desktop-popup.ps1 # Windows native popup (PowerShell + WPF)
├── desktop-popup.py # macOS/Linux native popup (Python 3 + tkinter)
├── cordis.patch.yml # DSH bundle patch for persistent mounting
├── test/
│ └── status-smoke.mjs # status-machine smoke test
├── tools/
│ └── mock-status.mjs # mock status service for offline popup testing
├── package.json # npm package + dsh.bundle declaration
├── README.md # English readme
├── README.zh.md # Chinese readme
├── CHANGELOG.md
├── CONTRIBUTING.md
└── LICENSE
Debug logs are written to:
~/.dsh/tn-plugin.log — host plugin lifecycle, popup launcher, question watcher.~/.dsh/tn-launcher.log — PID of the popup process created by the launcher.~/.dsh/tn-popup-debug.log — popup script lifecycle and polling errors.If the popup does not appear after restarting dsh web, check those logs first.
Note that popup launcher exit: code=0 in tn-plugin.log is expected: the plugin spawns a one-shot launcher which starts the real popup process and then exits.