Skip to content

Frost-Reed/blocker-notify

20Last commit Aug 14, 2026

blocker-notify DSH plugin

blocker-notify is a persistent DSH web plugin with host and client components. It surfaces actionable agent blockers through a global banner, flashing workspace indicators, optional chimes, and browser OS notifications.

How to install the blocker-notify DSH plugin

dsh plugin --profile web add github:Frost-Reed/blocker-notify

Copying does not run this command. Review the repository and version before use.

Data source

Snapshot date: Aug 15, 2026

manifest-valid

What the blocker-notify DSH plugin can do

  • Detects pending approval requests, user questions, and plan-review interactions.
  • Shows a global banner listing blocked sessions and their status.
  • Adds a flashing animation to DSH warning indicators for blocked workspace sessions.
  • Plays a synthesized Web Audio chime only for newly detected actionable blockers.
  • Uses the browser Notification API for OS-level notifications when permission is enabled.
  • Provides session navigation from banner and notification interactions.
  • Records sandbox-denial events for host-side diagnostics while intentionally keeping them silent for users.
  • Supports persistent installation through a dsh.bundle package and a non-persistent dynamic-plugin workflow.

Where the blocker-notify DSH plugin fits

  • Monitoring long-running agent work without continuously watching the DSH web interface.
  • Responding quickly to permission approvals or sandbox escalation requests.
  • Returning to sessions where an agent is awaiting an answer or plan review.
  • Highlighting actionable interruptions across multiple workspace sessions.

Who the blocker-notify DSH plugin is for

  • DeepSeek Harness web users
  • Users supervising multiple agent sessions
  • Developers testing DSH approval and sandbox workflows

blocker-notify DSH plugin limitations

  • The dynamic-plugin workflow is in-memory and must be re-enabled after DSH restarts.
  • Persistent bundle installation requires restarting the DSH web process after adding the dependency/layer.
  • OS notifications depend on browser Notification API support and granted permission.
  • Audio may silently degrade when browser autoplay is unavailable or the environment does not support it.
  • Sandbox-denial events are intentionally logged for diagnostics but do not create user-facing alerts.
  • Git-based installation may invoke the prepare build script and require pnpm build authorization.

Objective checks

These signals come from public metadata scans. They are not a security certification.

  • dependency counts

    package.json declares 0 runtime, 2 development, 3 peer, and 0 optional dependencies.

    info
  • dsh bundle declared

    package.json declares DSH bundle metadata.

    info
  • license declared

    GitHub reports the repository license as MIT.

    info
  • package manifest available

    A root package.json was captured and can be inspected by the registry.

    info
  • prepare script detected

    package.json declares a prepare lifecycle script that may run during relevant package installation workflows.

    info
  • source available

    Public GitHub source metadata is available for this registry snapshot.

    info

blocker-notify DSH plugin alternatives

blocker-notify DSH plugin questions

What is the blocker-notify DSH plugin?

blocker-notify is a project included in the current DSH plugin snapshot. This page organizes repository metadata and reviewed notes, but you should still inspect the upstream repository before running it.

How do I install the blocker-notify DSH plugin?

The page shows the install command captured from the source record. Copying does not run it, so confirm the package, profile, and version against upstream documentation first.

Which DSH profile does blocker-notify use?

The snapshot records web as the blocker-notify profile. DSH conventions can change quickly, so verify the manifest and README before installation.

Is blocker-notify compatible with the current DSH release?

The source data does not include a verified compatibility matrix. Check recent commits, releases, and DSH breaking changes, then test in a profile you can roll back.

What should I do if blocker-notify fails to load?

Check the install command, selected profile, dependency logs, and Cordis startup output first. Keep the exact error string, then compare it with this site's fix pages and upstream issues.

What are the closest alternatives to blocker-notify?

Related plugins on this page come from the current snapshot and are only candidates. Compare capabilities, maintenance activity, installation method, and limitations before choosing one.