Task Notifier
ReviewAudited by ClawScan on May 18, 2026.
Overview
Task Notifier appears to be a coherent desktop-notification plugin, but it does run local OS commands as a startup plugin and asks users to bypass OpenClaw's unsafe-install warning.
This looks reasonable for a desktop notifier, but it is not just documentation if you install the runtime plugin. It will run at startup, execute local OS notification commands, check active window titles, and write small state files in workspaces. Review the source, understand the --dangerously-force-unsafe-install flag, and use the documented filters if you do not want it watching all agents.
Publisher note
Calls native OS notification APIs (osascript/PowerShell) via child_process. No network access. No file writes outside OpenClaw workspace.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Installing the runtime plugin lets it run local notification commands on your machine when tasks start or finish.
The runtime plugin executes a bundled shell script to perform notifications. This is disclosed and central to the purpose, but it is still local code execution.
execFileSync(SHARED_SCRIPT, args, {
timeout: action === "done" || action === "blocked" ? 12e3 : 5e3,
stdio: "ignore",Install only if you are comfortable with a local plugin executing OS notification commands; review the bundled script before using the unsafe-install flag.
The plugin may read the title of your active window locally to decide whether to suppress a notification.
The script inspects the foreground app/window title to decide whether OpenClaw is active. That is purpose-aligned for spam suppression, but window titles can reveal local context.
tell application "System Events"
set frontProc to first application process whose frontmost is true
set frontApp to name of frontProc
try
set winTitle to name of front window of frontProcUse it only if you are comfortable with local foreground-window checks; adjust TASK_NOTIFIER_ACTIVE_MATCH or uninstall if this is not acceptable.
The plugin becomes enabled in OpenClaw and can observe lifecycle events across agent runs.
The installer grants the plugin lifecycle hook permission and adds it to the allowed plugin list. The visible plugin uses this for task-completion events, but it is a meaningful permission change.
cfg.plugins.entries[pluginId].hooks.allowConversationAccess = true; ... cfg.plugins.allow = nextAllow;
Confirm you want this plugin enabled globally; review OpenClaw plugin settings after installation and remove it from plugins.allow if you no longer use it.
A user may be nudged to accept a dangerous-install flag without fully considering that it installs code that runs on startup.
The instructions encourage reassurance around an unsafe-install override. The visible behavior is disclosed and purpose-aligned, but users should not treat the override as risk-free.
Before running, reassure the user about the `--dangerously-force-unsafe-install` flag
Do not rely only on the reassurance text; review the source and permissions before approving the runtime plugin install.
Once installed, the notifier runs in the background with OpenClaw until disabled or removed.
The runtime plugin is configured to start automatically. This is expected for background task notifications, but it means the behavior persists after installation.
"activation": {
"onStartup": true
}Install it only if you want persistent background notifications; use the documented include/exclude environment variables or disable the plugin if it is too broad.