dsh-image-router

Text-only models in DSH hit a dead end the moment an image enters the conversation. The usual workaround is to swap to a multimodal model mid-session, which means a jumpy model selector, a [model changed] banner, and a session history that looks like two different models are taking turns. dsh-image-router sidesteps all of that: before you hit send, a vision model you designate quietly turns the image into a paragraph of text and substitutes it into the prompt. Your conversation model never changes, the selector stays put, and the log records a text analysis instead of an image block. From the model's point of view it simply received a longer piece of text.

Feeding the vision model is flexible. If you already have a multimodal model configured, pick it from a dropdown that only lists image-capable entries. If you have a separate vision API, fill in base URL, model name, and API Key, and the plugin translates that into a single upstream route without touching any of your existing provider definitions. Beyond inline images, any model can call the describe_image tool to analyze an on-disk image file on demand, because the image never enters the session and thus never hits the route-must-declare-image gate. API Keys are written to a credential store once and stripped from every parsed result, config section, and card draft; a failed vision call simply lets the original request proceed so the host surfaces the real error rather than masking it.

Who is it for? DSH users whose primary model is text-only but who regularly deal with screenshots, annotated diagrams, or document images. Developers who want a single, consistent model context across a session and refuse to be interrupted by mid-conversation model swaps. And anyone with a self-hosted or third-party vision endpoint who wants to plug it into their DSH workflow without reconfiguring existing providers. Everything is set through a GUI card, takes effect on the very next prompt, and requires neither hand-written YAML nor a restart.