whendone-plus

name	whendone-plus
description	Automatically notify the user when long-running terminal commands finish (npm test, docker build, git push, etc.). The agent monitors command execution and sends a desktop notification on completion if the command ran longer than threshold (default 10s). Use when user asks to "notify me when done", "desktop notification when command finishes", "alert when done", or "tell me when this completes". Do NOT use for interactive commands (vim, nano, less, htop), commands that always complete in <5s, or streaming commands (tail -f).
triggers	["notify me when done","desktop notification","alert when done","tell me when this completes","notify when finished","ping me when","remind me when","notification on completion","when done"]
negatives	["interactive commands","vim","nano","less","htop","streaming commands","tail -f","short commands"]
license	MIT
compatibility	opencode
metadata	{"workflow":"automation","audience":"developers","version":"3.0.0"}

WhenDone Plus

Automatically notify when long-running commands complete.

How It Works

1. User runs a long command (e.g. npm test, docker build, git push)
2. The agent monitors the command execution time
3. If the command runs longer than the threshold (default 10s), the agent notifies the user on completion
4. Exit code is passed through

Workflow

Step 1: Detect long-running command

Identify commands likely to exceed threshold:

• npm test, npm run test, npx playwright test
• docker build, docker compose up, docker compose down
• git push, git pull, git clone
• pip install, npm install, pnpm install, yarn install
• cargo build, cargo test, go build, dotnet build
• Custom scripts, database migrations, data processing pipelines
• ffmpeg, rsync, scp, large file transfers

Step 2: Monitor execution

Start a background timer when the command begins. Track:

• Elapsed wall-clock time
• Peak memory usage (if available)
• Child process tree (for pipeline awareness)

Step 3: Notify on completion

Basic notification format:

✅ "Command finished: npm test completed in 142s (exit 0)"
❌ "Command finished: docker build failed in 89s (exit 1)"

Include:

• Command name (first word + key args)
• Execution time (rounded to seconds)
• Exit code (success/failure)
• Optional: memory peak, output file path if redirected

Step 4: Handle edge cases

• Commands completing under 10s: no notification (too fast to matter)
• Interactive/TUI commands (vim, nano, htop): skip (user is watching)
• Piped commands (e.g. npm test | grep error): monitor the pipeline, not the first process
• Backgrounded commands (): notify on background process completion