@openma/deepseek-harness-acp 0.4.13 → 0.4.14

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.
Files changed (2) hide show
  1. package/README.md +26 -25
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -31,13 +31,13 @@ touch your editor config — it reuses the key you saved in the dsh Web UI, or
31
31
 
32
32
  ## Two entry points, one embeddable plugin
33
33
 
34
- | | **A · Standalone server** | **B · dsh profile plugin** |
34
+ | | **A · dsh profile plugin (recommended)** | **B · Standalone server** |
35
35
  |---|---|---|
36
- | Best for | Getting started in one command | Living inside your dsh setup |
37
- | Install | `npm i -g @openma/deepseek-harness-acp` | `dsh plugin --profile acp add -w @openma/deepseek-harness-acp` |
38
- | Zed runs | `dsh-acp` | `dsh --profile acp` |
39
- | Harness | Your installed dsh — or the npm-installed peer when none exists | The dsh that owns the profile |
40
- | Composition | dsh-base + this bundle (profile machinery booted in-process) | dsh-base + this bundle + your profile's own patches |
36
+ | Best for | Normal installation and upgrades | Connecting an ACP client without managing a dsh profile |
37
+ | Install | `dsh plugin --profile acp add @openma/deepseek-harness-acp@latest` | `npm i -g @openma/deepseek-harness-acp` |
38
+ | Zed runs | `dsh --profile acp` | `dsh-acp` |
39
+ | Harness | The dsh that owns the profile | Your installed dsh — or the npm-installed peer when none exists |
40
+ | Composition | dsh-base + this bundle + your profile's own patches | dsh-base + this bundle (profile machinery booted in-process) |
41
41
 
42
42
  Both shapes share `$DSH_HOME`: the same credential store, settings, presets,
43
43
  and session logs as `dsh web` — conversations started in the Web UI can be
@@ -54,50 +54,51 @@ plugin used by other dsh applications: one Host composition can expose the
54
54
  same sessions, tools, presets, skills, and persistence through a transport
55
55
  chosen by the surface.
56
56
 
57
- ### A · Standalone server
57
+ ### A · dsh profile plugin (recommended)
58
58
 
59
59
  ```bash
60
- npm install -g @openma/deepseek-harness-acp
61
- dsh-acp login # interactive; or save the key in the dsh Web UI
60
+ npm install -g @deepseek-ai/dsh
61
+ dsh web # save your API key once
62
+ dsh plugin --profile acp add @openma/deepseek-harness-acp@latest
62
63
  ```
63
64
 
64
65
  ```jsonc
65
66
  // Zed settings.json
66
67
  {
67
68
  "agent_servers": {
68
- "DeepSeek Harness": { "command": "dsh-acp" }
69
+ "DeepSeek Harness": { "command": "dsh", "args": ["--profile", "acp"] }
69
70
  }
70
71
  }
71
72
  ```
72
73
 
73
- Self-contained: it finds your DeepSeek Harness via `--dsh-path` / `DSH_PATH`,
74
- its own tree, `./node_modules`, `dsh` on PATH, or `npm root -g` — and ships a
75
- npm-installed harness peer as the **last** candidate, so it works out of the box
76
- and always prefers the dsh you installed. When a real
77
- `$DSH_HOME/profiles/acp` exists, that profile owns the composition.
74
+ The plugin command creates `$DSH_HOME/profiles/acp`, installs or upgrades the
75
+ adapter, and registers its `dsh.bundle` patch. The bridge mounts over
76
+ `@deepseek-ai/dsh-base` — the same product baseline as `dsh web`, with the
77
+ module-reload watcher off. Extend the profile in
78
+ `$DSH_HOME/profiles/acp/cordis.patch.yml` like any other dsh profile. A global
79
+ `dsh-acp` installation is not required for this path.
78
80
 
79
- ### B · dsh profile plugin
81
+ ### B · Standalone server
80
82
 
81
83
  ```bash
82
- npm install -g @deepseek-ai/dsh
83
- dsh web # save your API key once
84
- dsh plugin --profile acp add -w @openma/deepseek-harness-acp
84
+ npm install -g @openma/deepseek-harness-acp
85
+ dsh-acp login # interactive; or save the key in the dsh Web UI
85
86
  ```
86
87
 
87
88
  ```jsonc
88
89
  // Zed settings.json
89
90
  {
90
91
  "agent_servers": {
91
- "DeepSeek Harness": { "command": "dsh", "args": ["--profile", "acp"] }
92
+ "DeepSeek Harness": { "command": "dsh-acp" }
92
93
  }
93
94
  }
94
95
  ```
95
96
 
96
- This creates `$DSH_HOME/profiles/acp` and registers the package's
97
- `dsh.bundle` patch: the bridge mounts over `@deepseek-ai/dsh-base` — the same
98
- product baseline as `dsh web`, with the module-reload watcher off. Extend the
99
- profile in `$DSH_HOME/profiles/acp/cordis.patch.yml` like any other dsh
100
- profile.
97
+ The standalone binary finds DeepSeek Harness via `--dsh-path` / `DSH_PATH`,
98
+ its own tree, `./node_modules`, `dsh` on PATH, or `npm root -g`. It ships an
99
+ npm-installed harness peer as the **last** candidate, so it still prefers the
100
+ dsh you installed. When a real `$DSH_HOME/profiles/acp` exists, that profile
101
+ owns the composition.
101
102
 
102
103
  ## Plugin and extension model
103
104
 
package/package.json CHANGED
@@ -3,12 +3,12 @@
3
3
  "publishConfig": {
4
4
  "access": "public"
5
5
  },
6
- "version": "0.4.13",
6
+ "version": "0.4.14",
7
7
  "repository": {
8
8
  "type": "git",
9
9
  "url": "git+https://github.com/openma-ai/deepseek-harness-acp.git"
10
10
  },
11
- "homepage": "https://github.com/openma-ai/deepseek-harness-acp#readme",
11
+ "homepage": "https://dshsuite.dev/#other-products",
12
12
  "bugs": {
13
13
  "url": "https://github.com/openma-ai/deepseek-harness-acp/issues"
14
14
  },