opencode-memoir 3.3.5 → 3.3.7
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 +14 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -38,7 +38,9 @@ does not block the `chat.message` hook.
|
|
|
38
38
|
|
|
39
39
|
## Store configuration
|
|
40
40
|
|
|
41
|
-
The plugin
|
|
41
|
+
The plugin derives a store path under `~/.memoir/` from the project repository.
|
|
42
|
+
Linked Git worktrees of the same repository share that store by default.
|
|
43
|
+
Override via `MEMOIR_STORE` env var or `store` plugin option:
|
|
42
44
|
|
|
43
45
|
```jsonc
|
|
44
46
|
{
|
|
@@ -48,6 +50,14 @@ The plugin delegates store path resolution to `memoir-mcp`. Override via `MEMOIR
|
|
|
48
50
|
}
|
|
49
51
|
```
|
|
50
52
|
|
|
53
|
+
Run only one active OpenCode instance per Memoir store. Concurrent instances
|
|
54
|
+
sharing a store are unsupported, including instances in different Git worktrees:
|
|
55
|
+
one instance can switch the store's branch while another is still capturing,
|
|
56
|
+
causing memories to be saved on the wrong branch. Finish one instance before
|
|
57
|
+
starting another, or configure a separate store for each concurrent instance.
|
|
58
|
+
Separate stores have independent memory and history. This restriction also
|
|
59
|
+
applies to multiple project instances hosted by a single OpenCode server.
|
|
60
|
+
|
|
51
61
|
## Environment variables
|
|
52
62
|
|
|
53
63
|
All optional:
|
|
@@ -88,7 +98,7 @@ completed turn: the incoming user message has not entered the transcript yet.
|
|
|
88
98
|
across parent sessions within each plugin instance. Snapshots are read immediately,
|
|
89
99
|
so a delayed earlier submission cannot make a later turn disappear from the queue.
|
|
90
100
|
An accepted capture is tracked before the next submission may switch branches;
|
|
91
|
-
switching waits for active captures to finish.
|
|
101
|
+
switching waits for active captures to finish. Within that instance, captures on the same branch can
|
|
92
102
|
continue running in parallel after submission. A hidden throwaway session is created
|
|
93
103
|
without a `parentID` and submitted through `promptAsync`. The hook itself does
|
|
94
104
|
not wait for that submission, and the subagent is instructed to store memories
|
|
@@ -144,5 +154,5 @@ removed after the check.
|
|
|
144
154
|
Releases are fully automated — no manual `npm version` or `npm publish`.
|
|
145
155
|
|
|
146
156
|
1. Land changes on `main` via PR using [Conventional Commits](https://www.conventionalcommits.org/) (`feat:`, `fix:`, etc.)
|
|
147
|
-
2. On push to `main`, `.github/workflows/semantic.
|
|
148
|
-
3. The new tag triggers `.github/workflows/publish-npm.
|
|
157
|
+
2. On push to `main`, `.github/workflows/semantic.yml` runs [semantic-release](https://semantic-release.gitbook.io/)
|
|
158
|
+
3. The new tag triggers `.github/workflows/publish-npm.yml`, which builds and runs `npm publish --provenance`
|