@dickpy/dsh-imagegen

Q: Does it collide with dsh-meme?

@dickpy/dsh-imagegen is the one to keep here: Generation covers more than sending; keep the meme library only if sending is the common case.

Q: What happens when dsh upgrades?

Nothing declares a version window for @dickpy/dsh-imagegen: dsh --version tells you what you are running, and no check will tell you whether @dickpy/dsh-imagegen matches it.

Text-to-image and image-to-image inside the web client, through a configured image provider.

Version 1.17.1 of @dickpy/dsh-imagegen, last published 2026-11-13; the install command and the range come from its own manifest.

Install

dsh plugin add @dickpy/dsh-imagegen writes one dependency line into the profile manifest; pnpm then unpacks it under $DSH_HOME/profiles/<name>/node_modules.

dsh plugin --profile web add @dickpy/dsh-imagegen

Compatibility

@dickpy/dsh-imagegen ships no engines.dsh entry, so nothing checks it against your CLI version at boot. Read the npm page before installing.

If two plugins fight

It puts an image path in the composer area, next to dsh-meme, which sends from a library instead of generating. Two buttons is the symptom, not an error.

Who made it

Author: dickpy. Repository: https://github.com/dickpy/dsh-imagegen. Package page: https://www.npmjs.com/package/@dickpy/dsh-imagegen.

After install

It declares no dsh peer and renders a renderer for answer blocks in conversation replies; after dsh plugin add @dickpy/dsh-imagegen, dsh --profile web --dump-config lists the @dickpy/dsh-imagegen row that mounts it.

Files it touches

No storage peer appears in the manifest of @dickpy/dsh-imagegen, so the dependency line in $DSH_HOME/profiles/<name>/package.json is the only file you can point at; the package description names nothing else.

Removing it

Removing @dickpy/dsh-imagegen is the mirror command, dsh plugin --profile web remove @dickpy/dsh-imagegen. Its manifest declares no storage peer, so it writes nothing under $DSH_HOME; removing it leaves no files behind.

Common questions

Does it collide with dsh-meme?

@dickpy/dsh-imagegen is the one to keep here: Generation covers more than sending; keep the meme library only if sending is the common case.

What happens when dsh upgrades?

Nothing declares a version window for @dickpy/dsh-imagegen: dsh --version tells you what you are running, and no check will tell you whether @dickpy/dsh-imagegen matches it.