ds-bot 0.1.0 → 0.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -1
- package/client.js +513 -71
- package/index.js +3 -1
- package/package.json +4 -1
- package/src/host/channel.js +12 -5
- package/src/host/dsh-update.js +168 -0
- package/src/host/groups.js +2 -0
- package/src/host/models.js +65 -8
- package/src/host/parts.js +18 -2
- package/src/host/permissions.js +42 -0
- package/src/host/roster.js +14 -1
- package/src/host/update.js +45 -40
- package/src/host/usage.js +26 -4
package/README.md
CHANGED
|
@@ -33,7 +33,7 @@ Tested with dsh `0.2.1-alpha.1` (Web and Desktop) on Linux.
|
|
|
33
33
|
|
|
34
34
|
The [project page](../README.md#install) has the full steps for dsh Desktop and dsh Web. In short:
|
|
35
35
|
|
|
36
|
-
- dsh Desktop: Settings → Plugins → add `ds-bot` (npm), a `.tgz` file, or `github:FeiZhuLulu/DeepSeek-Bot#v0.1.
|
|
36
|
+
- dsh Desktop: Settings → Plugins → add `ds-bot` (npm), a `.tgz` file, or `github:FeiZhuLulu/DeepSeek-Bot#v0.1.1&path:/ds-bot`.
|
|
37
37
|
- Command line: `dsh plugin --profile desktop add ds-bot` (or `--profile web`).
|
|
38
38
|
|
|
39
39
|
To work on the plugin from a checkout, add it to a dsh profile as a linked dependency and a bundle:
|
|
@@ -77,6 +77,8 @@ Options go in the profile's `cordis.patch.yml`, under the `bot` entry. All of th
|
|
|
77
77
|
|
|
78
78
|
**Updates**: when a window opens, DS Bot asks where it was installed from for a newer release: the npm registry (the one the DSH plugin manager installs from, then its fallbacks), or the latest GitHub release for a `github:…#vX.Y.Z` install. A newer version shows a cloud button at the top right of the sidebar; **Update** reinstalls DS Bot through the DSH plugin manager, and the new version runs from the next DSH start. A linked or local checkout is never offered an update.
|
|
79
79
|
|
|
80
|
+
The same card carries DSH itself: every DS Bot release names the DSH release it was verified against (`dsBot.verifiedDsh` in its `package.json`), and only that version is offered — running something newer is a downgrade offer too. A DSH installed from npm is swapped by `npm install -g @deepseek-ai/dsh@<version>`; a packaged app owns its runtime, so the card shows its current and verified versions and opens the app's own update panel. A release may raise the floor with `dsBot.minBot`: until the bot itself is that new, the DSH row waits.
|
|
81
|
+
|
|
80
82
|
## Models
|
|
81
83
|
|
|
82
84
|
Model providers are set up with dsh's `llm-pi-ai` plugin in `cordis.patch.yml`. Every Bot runs on one model of its own, from the models DSH serves. A new team's first Main Bot has none: its chat opens on a model card and it greets the user only after a pick. The Create Bot form starts on the DSH default model. The Bot's details panel and settings (or a Main Bot's `update_bot`) change it; a Bot whose model is no longer served shows the card again. A team saved by an older version keeps the model each Bot last ran on.
|