Files

T

Pine 768bcd4356 fix(image-recognition): keep the vision key on its own ref; add clear-key

Image recognition and the chat model shared DEEPSEEK_API_KEY: the
image-recognition bundle defaulted apiKeyEnv to the model key, so saving one
overwrote the other. Point the bundle at IMAGE_RECOGNITION_API_KEY and guard
both the provider and the settings card against a stale model ref, so vision
never reads or writes the chat key. Also add a clear-key button, default the
model to qwen3-vl-flash on the DashScope compatible-mode endpoint, and send
file images as base64 with a normalized base URL.

Co-Authored-By: Claude <noreply@anthropic.com>

2026-08-14 23:01:15 +08:00

src

feat(vision): add the opt-in image-recognition bundle

2026-08-14 10:58:29 +08:00

cordis.patch.yml

fix(image-recognition): keep the vision key on its own ref; add clear-key

2026-08-14 23:01:15 +08:00

package.json

feat(vision): add the opt-in image-recognition bundle

2026-08-14 10:58:29 +08:00

README.md

feat(app-boot): mount image recognition by default for the web profile

2026-08-14 11:48:17 +08:00

tsconfig.json

feat(vision): add the opt-in image-recognition bundle

2026-08-14 10:58:29 +08:00

README.md

@deepseek-ai/dsh-image-recognition-bundle

Opt-in image-recognition bundle for a profile. Its cordis.patch.yml mounts the capability seam (@deepseek-ai/dsh-image-recognition), the configurable HTTP provider (@deepseek-ai/dsh-image-recognition-http), and the model-facing consumer (@deepseek-ai/dsh-tool-image-recognition).

The web profile template mounts this bundle by default. A non-web profile opts in by adding this package to its dsh.profile.bundles (or dsh plugin --profile <name> add @deepseek-ai/dsh-image-recognition-bundle). Then configure the endpoint, key, and model in the Plugins settings page (image-recognition card).

Known Limitations and Deferred Work

Requires the user to supply a vision provider endpoint and key; recognition is unavailable until both are configured.