dsh-plugin-image-gen
通过配置的任意 OpenAI 兼容端点生成图像。本软件包不附带任何端点或凭据。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:HaoyanZhang123/dsh-plugin-image-gen#84b4fc8abdb9374110b8042bd66d5ea735bee52bPlugin Image Gen 以 dsh-plugin-image-gen 发布，当前版本为 0.1.2。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Generate images from inside DeepSeek Harness (DSH) through any OpenAI-compatible image endpoint you configure. The package ships no endpoint, no model list tied to a vendor, and no credentials - you bring all three.
It registers two agent tools:
| Tool | Purpose |
|---|---|
generate_image | Generate image(s) from a prompt and save them to disk; returns absolute path(s). |
get_image_gen_config | Show the effective configuration and setup diagnostics (never secret values). |
POST {baseURL}/images/generations, returning data[].b64_json or data[].url. This covers OpenAI itself and most relays/gateways.Nothing else: no system Node install, no dependencies, no build step.
In DSH's Plugins page:
github:HaoyanZhang123/dsh-plugin-image-gengithub:HaoyanZhang123/dsh-plugin-image-gen#v0.1.2.tgz from Releases and paste its absolute pathdsh-plugin-image-genA fresh install takes effect immediately - the next turn already has both tools. Upgrading an already-installed version is the one case DSH reports as restart-required: quit and reopen DSH afterwards (closing the window is not quitting; use the tray icon).
Everything lives there. Ask your agent to run get_image_gen_config - it prints the exact path in the "Config file" line. Or work it out:
| Platform | Default DSH home |
|---|---|
| Windows | %USERPROFILE%.dsh (for example C:\Users\you.dsh) |
| macOS / Linux | ~/.dsh |
| Any, if set | whatever DSH_HOME points to |
Pick whichever suits you:
/.credentials.yaml, under the existing refs: section:
refs:
IMAGE_GEN_API_KEY: your-api-key-here
IMAGE_GEN_API_KEY in the environment that launches DSH.IMAGE_GEN_API_KEY=your-api-key-here to /.env.Resolution mirrors the official DSH layering: process environment > .credentials.yaml refs > /.env > /.env.
Keys are never read from conversation, shown in tool output, or stored by this plugin. Do not paste your key into a chat message - put it in one of the three places above.
Create /image-gen.config.json:
{
"baseURL": "https://your-relay.example.com/v1",
"apiKeyEnv": "IMAGE_GEN_API_KEY",
"models": ["gpt-image-1", "another-model"],
"defaultModel": "gpt-image-1"
}
That is the whole setup for most people. Skip this step entirely if you are using OpenAI itself with the default values - just add the key in step 2.
Two practical notes:
baseURL is the part before /images/generations. If your gateway exposes images at https://gw.example.com/openai/v1/images/generations, set baseURL to https://gw.example.com/openai/v1."E:\images") or with forward slashes ("E:/images").Edits take effect on the next tool call - no restart.
Ask your agent to run get_image_gen_config. You want to see your endpoint, your models, and Resolved keys: 1 (or more). Then say "generate an image of a red apple on a white table" and check the returned path on disk.
Just describe the image. Overrides are per call and phrased naturally:
sizen=4Images are saved as PNG files and reported by absolute path, so they survive independently of the conversation. To view one in chat, the active model must accept image input - otherwise open the file.
| Field | Default | Meaning |
|---|---|---|
baseURL | https://api.openai.com/v1 | Any OpenAI-compatible base URL; POST /images/generations is called. |
apiKeyEnv | IMAGE_GEN_API_KEY | Credential name(s), comma-separated for rotation (for example KEY_A,KEY_B). Stores names, never keys. |
models | ["gpt-image-1"] | Model ids shown to the agent; it may pass any id. |
defaultModel | first of models | Used when a call does not specify model. |
defaultParams | {} | Extra request fields merged into every call - the escape hatch for provider-specific parameters such as aspect_ratio or style. |
timeoutMs | 240000 | Per-request timeout. |
outputDir | /image-gen/output | Where images are saved; per-call output_dir overrides. |
proxy | auto | auto (keep an environment proxy, else detect the OS system proxy: Windows registry / macOS scutil), off, or an explicit http://host:port. |
Layering: package defaults < the entry's optional config: block in the profile patch < image-gen.config.json.
size and quality are pass-through strings: they are sent only when you set them (per call or via defaultParams); otherwise the endpoint applies its own defaults. Vocabulary differs per provider - the plugin never validates them, and endpoint errors are returned verbatim so the agent can retry.
| Symptom | Cause and fix |
|---|---|
No API key found for "IMAGE_GEN_API_KEY" | Step 2 was skipped, or the key sits under a name that differs from apiKeyEnv. Run get_image_gen_config to see which names are consulted. |
Configuration warnings: ... invalid JSON | The config file failed to parse and was ignored; defaults apply. Validate the JSON and check for Windows backslashes. |
upstream HTTP 401 | The endpoint rejected the key (wrong key, wrong account, or a key for a different gateway). |
upstream HTTP 404 | baseURL is wrong - usually it already includes or omits /v1. The called URL is {baseURL}/images/generations. |
upstream HTTP 429 | Rate limited. Add a second key to apiKeyEnv (KEY_A,KEY_B); the plugin rotates on 401/429. |
upstream returned no image data | The endpoint answered, but not in OpenAI image shape (data[].b64_json / data[].url). It is not compatible. |
| Request timed out | Raise timeoutMs. Large sizes and high quality can take minutes. |
| Connection errors behind a proxy | Leave proxy: "auto", or set an explicit URL (including credentials if the proxy needs them). OS proxies requiring authentication are not picked up automatically. |
Anything else: the error text is returned verbatim from the endpoint, and get_image_gen_config reports the effective settings and config-file path.
files whitelist in package.json defines exactly what ships.npm run pack:check packs the tarball and scans every shipped file for key-shaped strings before a release.See COMPATIBILITY.md. In short: the plugin imports only Node builtins and the documented tool-registration contract, declares no DSH version gate at all, and fails loudly and locally if that contract ever changes. It is tested against DSH Desktop 0.2.0-rc.2 on Windows; macOS uses the same contracts (system-proxy detection covered by unit tests).
Remove the bundle in the Plugins page. Your image-gen.config.json, saved images, and credentials are left untouched.
node --test # 37 tests
node tools/check-package.mjs # file whitelist + credential-leak scan, then packs the tarball
Release flow: bump version in package.json, add a CHANGELOG entry, run both commands, commit, then gh release create vX.Y.Z dsh-plugin-image-gen-X.Y.Z.tgz.