Files

T

History

Pine 08ac7c3da5 feat(vision): gate recognition on a configured provider

Expose ImageRecognitionRuntime.available() and gate the image-task pre-step
injection on it, so the capability is dormant until an endpoint is
configured instead of guiding the model to a call that can only fail.

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

2026-08-14 12:08:30 +08:00

src

feat(vision): gate recognition on a configured provider

2026-08-14 12:08:30 +08:00

tests

feat(vision): gate recognition on a configured provider

2026-08-14 12:08:30 +08:00

package.json

feat(vision): add the image-recognition capability seam

2026-08-14 10:55:57 +08:00

README.md

docs(vision): package READMEs, Model Experience, and the capability Agent Note

2026-08-14 11:15:59 +08:00

tsconfig.json

feat(vision): add the image-recognition capability seam

2026-08-14 10:55:57 +08:00

README.md

@deepseek-ai/dsh-image-recognition

Service Definition for the image-recognition capability seam (ctx.imageRecognition): a provider registry and provider-selecting execution, mirrored on the web seam.

A provider registers via ctx.imageRecognition.registerProvider(provider); a duplicate id throws IMAGE_RECOGNITION_DUPLICATE_PROVIDER.
recognize(request, signal) resolves the provider at call time. Selection is order-independent: a configured id must be registered and available(); without a configured id, exactly one usable provider auto-selects. See the ImageRecognitionError codes for missing/unavailable/ambiguous providers.
ImageInput is a closed union of file-path, base64, and url; a provider encodes the kind it serves.

Config

provider pins which provider wins; $DSH_IMAGE_RECOGNITION_PROVIDER is the environment equivalent (not a hidden priority chain).

Known Limitations and Deferred Work

The seam is provider-neutral by design; image decoding/encoding lives in the provider, not here.
ImageRecognitionError codes are open-string and provider-specific codes are tolerated by consumers.