Manage your Yuanliu account, groups, and models in DSH.
中文 | English
元流 Models
Sign in to your 元流 account in DSH and select platform models for chat. The plugin provides a separate settings page in Chinese and English, following the DSH interface language. The official Models page remains available for manually configured providers.
Installation and First Use
Requires DSH 0.2.1-rc.2 or newer and its official remote-call, settings, credential and model adapter interfaces.
- Install the plugin with the DSH plugin manager.
- Open Settings → 元流 Models and sign in with your platform email and password.
- Select the models you need and adjust group and model settings as appropriate.
- Choose Save changes, then select an enabled model in chat.
If no models are available after signing in, confirm that the platform account has a valid API key bound to an available model group, then refresh the catalog. The plugin reads existing group keys and does not create API keys.
The screenshot shows the signed-out page in an isolated DSH instance; the interface is shown in Chinese.
Using Settings
- The account bar shows connection status and balance. The refresh icon beside the balance updates only the balance; account settings manage your session.
- Select all models or a group, search and select models, then save your changes.
- Refreshing the catalog reloads groups and models while retaining unsaved edits. It is separate from refreshing the balance.
- Use a model's settings to adjust its name, context, maximum output and capabilities. Select a group to adjust its display name, enabled state and protocol.
- Startup synchronization failures show the failed stage and a safe error code. Check connectivity, account permissions or local settings before retrying.
Models and Capabilities
Newly discovered models are disabled until selected and saved. Groups with valid keys appear even when they have no models. Group and model names, ordering and enabled states can be adjusted; groups support Responses and Chat Completions protocols.
Capabilities use platform information where available, supplemented by bundled model specifications and applicable model-name inference. Saved manual overrides take precedence. Context is the total token budget for input and output; maximum output does not increase that budget. The bundled specification snapshot comes from models.dev (2026-10-20); actual availability depends on the platform.
Preferences are stored locally through the official DSH settings service. Refreshing the catalog retains preferences and unsaved changes, which still need to be saved.
Accounts and Credentials
DSH's credential service stores the platform session, catalog cache and API keys. Model configuration contains credential references, not raw keys. Remember password is optional and off by default. When enabled, the password is protected by Windows DPAPI, macOS Keychain, or a key stored in Linux Secret Service. Linux requires an unlocked Secret Service and secret-tool. If secure storage is unavailable, an error is shown rather than storing the password in plaintext. Legacy plaintext remembered passwords are migrated when read; a failed migration retains the original record for retry.
Even without remembering the password, the plugin saves the login session. During an upgrade, retaining the plugin ID, platform and gateway addresses, and DSH credential store allows the plugin to attempt session restoration. Temporary network or catalog errors do not deliberately sign the account out. Sessions with a refresh token attempt automatic renewal when the access token expires; older sessions without one need to sign in once to obtain it. A failed or expired refresh token, or failure to save the renewed session, may require signing in again.
Saved provider configuration is restored before credentials and the platform catalog are refreshed. On the first migration from an older version, the welcome check can run before legacy key migration completes. The actual installed desktop restart flow has not been verified.
Older provider entries cannot be reliably distinguished from manual configuration and are preserved. If a provider name conflicts after upgrading, inspect and back up the entry, remove it in the official Models settings only if it is no longer needed, then retry.
Signing out removes this plugin's saved login credentials, remembered password and API key references, and removes managed provider entries that have not been manually changed. Manual and older entries remain, as do local model and capability preferences. Failed cleanup is reported and pending references are retained for retry.
Compatibility
The plugin uses official DSH settings, credentials and model adapter interfaces, and public SDKs for Responses and Chat Completions. Available models, protocols and capabilities depend on account permissions and gateway support.