dsh-plugin-sessiongraph 0.1.15 → 0.1.17
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 +4 -0
- package/package.json +5 -5
package/README.md
CHANGED
|
@@ -103,6 +103,10 @@ Memory does not overlap with either: a conversation may **never enter memory** (
|
|
|
103
103
|
|
|
104
104
|
Prefer to drive it yourself? `autoBuild: false` disables the first automatic build and `autoIndex: false` disables the incremental refreshes; everything then goes through `sessiongraph_index` / `/sessiongraph index`.
|
|
105
105
|
|
|
106
|
+
### When the registry has a newer release
|
|
107
|
+
|
|
108
|
+
**It says so once, after a tool runs.** A plugin cannot upgrade itself — it lives in a profile's dependency tree, and rewriting that tree is the host's job. So it does the next best thing: after one of its tools runs, it checks the registry in the background and, when the published version is newer than the running one, appends a notice to the next step of the conversation, where both the model and the user can see it. Three details keep it from turning into noise: the check only ever happens *after* a tool was used; a release is announced once, with `notifiedVersion` persisted so a desktop restart does not replay it; and checks run at most every six hours, while an unreachable registry, a timeout, or an unwritable state file all mean "nothing to report" rather than an error. The registry follows npm's own resolution order — `npm_config_registry`, then `registry=` in the user's `~/.npmrc`, then npm's public default — so a machine behind a mirror checks the mirror it actually installs from. `updateCheck: false` turns the whole thing off, and `updateCheckIntervalMs` changes the interval.
|
|
109
|
+
|
|
106
110
|
### What gets indexed
|
|
107
111
|
|
|
108
112
|
`user/message` (only `source.kind === 'user'`, i.e. text a human typed), the `text` blocks of `assistant/message` (`reasoning` is 61% of the bytes and is not indexed), `tool/call` names and arguments, and `session/title`. Skipped: `tool/result` bodies, `request/header`, `step/*`, `job/*`.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "dsh-plugin-sessiongraph",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.17",
|
|
4
4
|
"description": "Bundle for the sessiongraph capability — install this package to add local conversation-history search to a DeepSeek Harness profile",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"dsh",
|
|
@@ -30,10 +30,10 @@
|
|
|
30
30
|
"provenance": false
|
|
31
31
|
},
|
|
32
32
|
"dependencies": {
|
|
33
|
-
"dsh-plugin-sessiongraph-
|
|
34
|
-
"dsh-plugin-sessiongraph-
|
|
35
|
-
"dsh-plugin-sessiongraph-
|
|
36
|
-
"dsh-plugin-sessiongraph-
|
|
33
|
+
"dsh-plugin-sessiongraph-sessions": "^0.1.17",
|
|
34
|
+
"dsh-plugin-sessiongraph-sqlite": "^0.1.17",
|
|
35
|
+
"dsh-plugin-sessiongraph-service": "^0.1.17",
|
|
36
|
+
"dsh-plugin-sessiongraph-tool": "^0.1.17"
|
|
37
37
|
},
|
|
38
38
|
"dsh": {
|
|
39
39
|
"bundle": {
|