Skip to content

superagents-lab/dsh-s1

30Last commit Aug 14, 2026

dsh-s1 DSH plugin

dsh-s1 integrates s1.dev's API directly into DeepSeek Harness as first-class DSH tools. It provides five native tools (s1_search, s1_news, s1_crawl, s1_sitemap, s1_trending) and a bundled skill to help the model choose the right tool.

How to install the dsh-s1 DSH plugin

dsh plugin --profile web add dsh-s1

Copying does not run this command. Review the repository and version before installing the dsh-s1 DSH plugin.

dsh-s1 DSH plugin data source

dsh-s1 DSH plugin snapshot date: Aug 16, 2026

discovered

What the dsh-s1 DSH plugin can do

  • s1_search: perform web searches via Search1API
  • s1_news: fetch news results from Search1API
  • s1_crawl: crawl web pages via Search1API
  • s1_sitemap: retrieve sitemaps via Search1API
  • s1_trending: get trending topics via Search1API
  • Bundled s1 skill that teaches the model tool selection and parameter tuning
  • Per-tool enable/disable via config (search, news, crawl, sitemap, trending, skill)

Where the dsh-s1 DSH plugin fits

  • Quick web lookups during conversations with DeepSeek models
  • News monitoring and trend analysis via s1_news and s1_trending
  • Web scraping and content extraction using s1_crawl
  • Site structure exploration through s1_sitemap

Who the dsh-s1 DSH plugin is for

  • DeepSeek Harness users who need web search capabilities
  • Developers building AI agents that require real-time web data

dsh-s1 DSH plugin limitations

  • Requires a valid S1_KEY environment variable for API authentication
  • s1_screenshot and s1_deepcrawl tools are not yet implemented
  • OAuth login flow is not supported; only API key authentication is available
  • The plugin depends on the @search1api/client SDK

dsh-s1 DSH plugin: from the repository README

Quoted from the superagents-lab/dsh-s1 README, the upstream source of the dsh-s1 DSH plugin. Copyright remains with the original authors.

Native [s1](https://s1.dev) tools for the [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) (DSH). Unlike the MCP server (`search1api-mcp`, a generic bridge that surfaces as `mcp__search1api__*`) or the CLI skill (which teaches the model to shell out to `s1`), this package registers **first-class DSH tools** named `s1_*` — same layer as `read`, `bash`, `subagent`, `workflow`. Calls run in-process against the official [`@search1api/client`](https://www.npmjs.com/package/@search1api/client) SDK. ## Tools | Tool | Backed by | Status | |------|-----------|--------| | `s1_search` | `Search1API.search()` | ✅ | | `s1_news` | `Search1API.news()` | ✅ | | `s1_crawl` | `Search1API.crawl()` | ✅ | | `s1_sitemap` | `Search1API.sitemap()` | ✅ | | `s1_trending` | `Search1API.trending()` | ✅ | Not yet implemented: `s1_screenshot` (needs DSH attachment/image support) and `s1_deepcrawl` (long-polling task). ![s1_crawl in DeepSeek Harness](assets/dsh-s1.png) ## Skill The package also bundles a `s1` skill (`ctx.skills.register`), which teaches the model how to pick the right tool and tune parameters — quick lookup vs deep research, source/recency signals, Chinese-query engine c

Read the full READMERepository license: MIT

dsh-s1 DSH plugin questions

How do I install dsh-s1?

Run `dsh plugin --profile web add dsh-s1` after publishing the package. For local development, use `npm link` or a file path: `dsh plugin --profile web add file:/path/to/dsh-s1`. The plugin then appears in your DSH profile's bundle stack.

What environment variable do I need to set?

You must set the `S1_KEY` environment variable to your Search1API API key. The SDK reads this key lazily, so a missing key will only cause tool call failures, not plugin activation errors.

Which tools are included?

The plugin registers five native tools: `s1_search`, `s1_news`, `s1_crawl`, `s1_sitemap`, and `s1_trending`. It also bundles a `s1` skill that helps the model select the right tool and tune parameters.

Can I disable individual tools?

Yes. In the plugin config you can set `search`, `news`, `crawl`, `sitemap`, `trending`, and `skill` to `false` to disable each one. By default all are enabled.

Does the plugin support OAuth?

Not yet. The OAuth flow (browser login, PKCE, token refresh) is only available in the `search1api-cli` tool. The plugin currently only supports API key authentication. OAuth support is planned but not implemented.