[MarioZZJ]

Listing

Add agent-notify-hooks as a kind: "hooks" entry, with an immutable hosted icon and English/Chinese summaries. The package is independently maintained in MarioZZJ/cc-notify-hooks; it declares magpie.hooks and has no provider or main/exports entry.

Publication prerequisite: this PR is a draft because agent-notify-hooks is not yet published on npm. Please do not merge until the npm package is available. The package is currently installable from GitHub:

magpie plugin add github:MarioZZJ/cc-notify-hooks

The registry entry deliberately uses the npm name, without unsupported GitHub source or spec fields. Once npm publication is complete, this draft can be marked ready.

Behavior and distinction

The hook provides per-channel delayed delivery and cancels pending notifications when the next request for the same session arrives. It reuses the cc-notify-hooks configuration and shell senders used by the companion Claude Code, Codex and dsh integrations. It supports 11 channels, including macOS, Pushover, Slack and Discord.

The existing @magpie-community/gateway-notify offers duration-based turn tracking, account sign-in notifications and an embedded configuration page. This package focuses on independently delayed channel queues and reusing an existing cross-agent configuration. The distinction is also described in its README and registry summaries.

Completed model responses are labelled as model responses, not as a guarantee that an agent task has ended. Tool-call responses and explicit subagents are skipped, and a missing session id is skipped rather than sharing an unknown-session queue.

Dependencies and data

• Requires Bash, jq and curl; macOS desktop notifications use osascript.
• Uses user-configured notification destinations and credentials in local JSON.
• Notifications include response excerpts by default. Rich channel messages can include project/session information, working directory, hostname and model.
• The shell dispatcher writes its normalized notification event to a local debug log; this package does not promise automatic log expiry.
• No provider authentication, MCP tools or account discovery are added.

Scope and checks

Only registry.json is changed. The entry uses fields declared in scripts/registry.mjs; local tests were not run. npm availability and a client installation from the registry remain pending.

[yetone]

Thanks @MarioZZJ. Noted that this waits for npm publication. Two things for when it's ready:

• Every other entry outside this repo's own packages carries "community": true; this one doesn't, so the Plugins page would show it like a first-party package. Please add it.
• Because the package runs shell senders and posts response excerpts to outside services (Slack, Discord, Pushover…), a listing like this waits for the maintainer to look at it before review and merge, even once it's on npm. I'll review and run it on a test box after that.