Introduction¶
DeepSeek Harness (DSH) adopts an “everything is a plugin” architecture. When integrating with local desktop apps or specific models, developers often face cumbersome configuration or lack an API Key. DSH Loomy Connect solves this pain point by allowing you to directly use the text models built into the Loomy desktop app, without requesting an additional API Key.
What It Is¶
DSH Loomy Connect is a plugin maintained by gdrpzym. It reads Loomy’s persisted login state and model list in read-only mode, and registers them as a model Provider for DSH.
Core Features¶
-
Zero configuration
After installation and activation, Loomy’s models appear directly in DSH’s model selector, with no manual parameter configuration required. -
Automatic model discovery
On startup, the plugin fetches the model list available to the current Loomy account and automatically filters for models that support text output. -
Account and credit management
In DSH’s settings card, the top status line displays the currently logged-in account (masked phone number).
The “Credits” tab shows permanent credits and daily bonus credits, using the same data source displayed by Loomy itself. -
Model details
In the “Models” tab of the settings card, a three-column table displays each model’s name, context window size (if provided in the model list), and credit multiplier (for example, x3.0, limited-time free). -
Chinese-English bilingual support
Card copy follows DSH’s interface language and switches automatically.
Installation and Activation¶
Before use, make sure your environment meets the following conditions:
* The Loomy desktop app is installed and has been used to log in.
* The DeepSeek Harness version is >= 0.1.5-rc.1.
Run the following command to install it:
dsh plugin --profile web add github:gdrpzym/dsh-loomy-connect
After installation, start the DSH Web service:
dsh web
To verify that the plugin is active, run the configuration dump command:
dsh --profile web --dump-config
Finding the llm-loomy entry in the output indicates successful registration. Then look for Loomy in the model selector.
Configuration and Notes¶
Path Configuration¶
By default, the plugin automatically detects Loomy’s data path, so manual configuration is usually not required. If path detection fails (for example, the login state is not detected on Windows), you can override it with environment variables:
LOOMY_AUTH_FILE: Login state file pathLOOMY_CONFIG_FILE: Model list file pathLOOMY_LOCAL_STORAGE_DIR: Credit cache directory
Security Boundaries¶
The plugin runs with the permissions of the current DSH process and is designed with the following security features:
* Read-only operations: It only reads files persisted by Loomy; it does not copy, upload, or rewrite any files.
* Local gateway: The internal gateway binds only to 127.0.0.1.
* Authentication: Client authentication uses timingSafeEqual comparison.
Limitations and Notes¶
- Loomy dependency: It must rely on Loomy’s client interface. If Loomy updates cause interface changes, the plugin may need adjustments.
- Data synchronization: The model list is fetched only at startup. After models are added or removed on the Loomy side, restarting DSH is required to synchronize.
- Credit cache: Credits are read from Loomy’s local cache. If the cache does not exist, the card will not display credits, rather than showing 0.
- Scope of use: For personal study and research only; do not use for commercial purposes.
Conclusion¶
DSH Loomy Connect provides seamless integration from local desktop apps to DSH. For developers already using Loomy, it is a convenient way to leverage existing resources without an additional API Key.