Skip to content

Add Webhound plugin 0.1.1#2767

Open
mfkhalil wants to merge 1 commit into
langgenius:mainfrom
mfkhalil:add-webhound-0.1.1
Open

Add Webhound plugin 0.1.1#2767
mfkhalil wants to merge 1 commit into
langgenius:mainfrom
mfkhalil:add-webhound-0.1.1

Conversation

@mfkhalil

Copy link
Copy Markdown

Plugin Submission

Plugin information

Submission type

  • New plugin
  • Version update

What changed

Adds Webhound as a Dify tool plugin for controllable, inspectable open-web investigations. It provides seven focused actions covering account checks, starting reports and datasets, watching progress, retrieving final outputs, retrieving evidence packs, and help. Research starts with an explicit dollar budget and confirm_spend=true; the package contains no shared or publisher API key.

Risk level

  • Low risk
  • Medium risk
  • High risk

Selected conservatively because Webhound can investigate open-web topics and prompts may contain sensitive or personal information. The plugin itself only connects to the fixed Webhound HTTPS API endpoint described below.

Required checks

  • I have read and followed the Marketplace submission requirements.
  • I have read and comply with the Plugin Developer Agreement.
  • I tested this plugin on Dify Community Edition and Dify Cloud, or documented any limitation below.
  • The package contains only files needed at runtime.
  • The package does not contain secrets, local credentials, .env files, .git directories, virtual environments, caches, logs, or IDE files.
  • The package does not contain executables or bundled binaries, or I explained why they are required below.
  • The plugin README includes setup steps, usage instructions, required APIs or credentials, connection requirements, and the source repository link.
  • The plugin includes PRIVACY.md or a hosted privacy policy, and manifest.yaml references it.
  • All user-facing text is primarily in English, with any localized README files following the i18n guidance.

Security and privacy notes

  • Each Dify workspace supplies its own Webhound API key. Dify stores the credential; no publisher credential is embedded or shared across users.
  • The plugin sends prompts, tool arguments, session IDs, and ordinary network metadata to Webhound. Prompts and investigated materials may contain personal data depending on the user's research request.
  • The plugin calls only https://api.webhound.ai/api/v2. It rejects redirects, does not let the user choose another API host, and does not automatically retry requests.
  • The plugin does not execute shell commands, code, SQL, SSH/SFTP, access local files, automate a browser, or proxy arbitrary user-selected URLs. Webhound's hosted service performs the requested open-web research.
  • Only the report-start and dataset-start tools can initiate paid research. Both require an explicit dollar budget and confirm_spend=true. The plugin is free; Webhound is an external paid service using the connected workspace's own account and credits.

Local validation

  • Ruff lint: passed.
  • Test suite: 29 tests passed.
  • Package inspection: 25 runtime files; no forbidden files, secrets, executables, bundled binaries, caches, environments, logs, or IDE artifacts.
  • Package SHA-256: b1c835ae9c807b9e07677fe387430636fe546f58d5be356e3d5f9b6a0ae2a489.
  • Dify Cloud: all seven tools exercised, including an exact-$1 report run through done=true and evidence-pack retrieval.

Reviewer notes

  • Minimum Dify version: 1.14.2.
  • Dify Community Edition was not separately exercised; this is the documented limitation covered by the required-check wording above.
  • Package path: webhoundai/webhound/webhound-0.1.1.difypkg.
  • This is a package-only submission with one changed file.

Submit the Webhound research plugin package to Dify Marketplace.
@github-actions github-actions Bot added the risk: high High-risk Marketplace submission label Jul 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk: high High-risk Marketplace submission

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant