Pine
768bcd4356
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>
29 lines
1.2 KiB
YAML
29 lines
1.2 KiB
YAML
# The dsh-image-recognition-bundle patch: an opt-in image-recognition surface
|
|
# over dsh-base. It is NOT part of any default profile's bundles list — a user
|
|
# opts in by adding this package to the profile's dsh.profile.bundles (or via
|
|
# `dsh plugin --profile <name> add @deepseek-ai/dsh-image-recognition-bundle`).
|
|
#
|
|
# The seam row pins the http provider; the provider row carries the credential
|
|
# reference the provider resolves per recognition; the consumer row toggles the
|
|
# deterministic image-task injection.
|
|
|
|
- insert:
|
|
- id: image-recognition
|
|
name: '@deepseek-ai/dsh-image-recognition'
|
|
config:
|
|
provider: http
|
|
|
|
- id: image-recognition-http
|
|
name: '@deepseek-ai/dsh-image-recognition-http'
|
|
config:
|
|
# Image recognition has its own credential plane, distinct from the
|
|
# chat model's. Pointing this at DEEPSEEK_API_KEY would let a save here
|
|
# overwrite the model's key (and vice versa); use the dedicated ref.
|
|
apiKeyEnv: IMAGE_RECOGNITION_API_KEY
|
|
|
|
- id: tool-image-recognition
|
|
name: '@deepseek-ai/dsh-tool-image-recognition'
|
|
config:
|
|
detectImageBlocks: true
|
|
detectImagePaths: true
|