sanshanya/better-model-provider

Per-model capability declaration for DeepSeek Harness: reasoning-effort levels (wire spellings) + request moda

better-model-provider is a per-model capability editor for DeepSeek Harness: two per-model fields that stayed YAML-only (reasoningEfforts and input) plus contextWindow/maxTokens become editable in a Settings page — one row fully configures one model. For custom models you edit declarations; for official-catalog routes you edit sparse overrides (everything else keeps following catalog updates), and installed-but-unconfigured official providers can be unfolded into routes from the same page. The picker then shows effort controls, image sessions accept the model, and capacities display in K/M spelling (380K, 1M); changes take effect at once.

Coding & Development ★ 6 updated 2026-09-11 ✅ runtime-tested
View on GitHub ↗

Install

dsh plugin --profile web add github:sanshanya/better-model-provider#master

GitHub bundle install per README: dsh plugin --profile web add github:sanshanya/better-model-provider#master. CI rebuilds and republishes ready-built artifacts to the master branch on every green main push, so this path never builds locally. Installing the default branch (github:sanshanya/better-model-provider) builds from source and prints one pnpm allowBuilds key to add, then rerun add; a local link: install must npm install && npm run build first. Restart dsh web — the Settings sidebar gains 'Model capabilities'. Remove: dsh plugin --profile web rm better-model-provider.

Compatibility

Whole dsh 0.1.x line: contract @deepseek-ai/dsh-api-remotes >=0.1.0-rc.7 <0.2.0; real-harness lanes verified on rc.7, rc.8, and 0.1.1-rc.2. Edits per-model reasoningEfforts (with wire spellings), input modalities, and token capacities (contextWindow / maxTokens). Custom models: edit declarations. Official models: edit overrides (only the difference from the official default is stored; Reset to official defaults undoes one model's edits). Dedicated-adapter apps (built-in DeepSeek / OpenAI Codex) declare capabilities on their own pages and never appear here. MIT.

Details

Recent updates

The current bilingual README (English primary) documents: why (two YAML-only fields), install (master branch path vs source build), use (configure provider/API key on the official Models page first, expand a model row, edit capabilities), official-model overrides and reset, manage official providers, compatibility contract, and license.

FAQ

Why do some models refuse image input?
Until the input modality is declared, the model's catalog entry says it does not accept images. This page lets you check 'image' under input modalities for the models that actually support it.
Does editing official models break catalog updates?
No — every change on an official route stores only the difference from the official default; everything else keeps following catalog updates. Reset to official defaults undoes all of one model's edits at once.
Where do I configure API keys?
Always on the official Models page — keys and route lifecycle are managed there; this page does not repeat them and only reads the provider routes you have configured.

Alternatives

sanshanya/better-model-provider · akemimadoka-dsh-model-configurator · omdsh-dev/dsh-llm-fallbacks

More plugins in Coding & Development

Browse more in Coding & Development

Guides for Coding & Development plugins