AI Agent Hub
Back to plugins
🧰

dsh-user-agent

Web Tools Updated 2026.08.22

Run the following command in DeepSeek Harness:

dsh plugin install dsh-plugins/dsh-user-agent

Paste the following prompt into your AI chat to install this plugin:

Install it in DeepSeek Harness by running dsh plugin install dsh-plugins/dsh-user-agent — source: https://github.com/dsh-plugins/dsh-user-agent

About this plugin

In DeepSeek Harness, every outgoing HTTP request — whether from an LLM adapter, a web-search tool, or a third-party plugin — ships its own distinct User-Agent. The result is a patchwork of identity strings that makes upstream logs hard to read and leaves no single place to standardise them. dsh-user-agent solves that by wrapping the global fetch once, so every outbound call carries the User-Agent you choose.

The mental model is one switch and one text field. Open Settings → UA settings in the Web GUI, flip the toggle, type the string you want, and hit Save. The very next request picks it up — no restart. The value lives in the standard dsh-user-agent settings namespace, so it persists across sessions and is editable from any settings-aware surface. When the plugin stops, updates, or is removed, the original fetch is restored cleanly, leaving no residue in the runtime.

If you need a consistent fingerprint in upstream logs, a single point of control for compliance, or simply prefer a recognisable string over the default, this is the lowest-effort way to get there without touching every caller.

Use Cases

  • Swap the User-Agent on every outbound request from the Web GUI — changes apply to the very next request, no restart needed
  • Give LLM API calls, web-search, and tool requests a single recognisable fingerprint in upstream logs
  • Standardise the egress identity of all HTTP traffic to meet compliance or audit requirements
  • Replace the per-plugin default User-Agent with one global, brand-consistent string

Best For

  • Ops and security teams who need to identify DeepSeek Harness traffic in upstream logs
  • Compliance and audit staff who want a single control point for outbound HTTP identity
  • Developers who prefer a custom User-Agent string over the built-in default