@lore-co/opencode 0.1.23 → 0.1.24
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 +64 -5
- package/package.json +5 -5
package/README.md
CHANGED
|
@@ -8,7 +8,8 @@ Most people should not install this package by hand. `lore connect` adds it to
|
|
|
8
8
|
OpenCode's plugin list and writes the workspace credentials.
|
|
9
9
|
|
|
10
10
|
```sh
|
|
11
|
-
|
|
11
|
+
curl -fsSL https://uselore.co/install.sh | bash
|
|
12
|
+
lore connect --login --agent opencode
|
|
12
13
|
lore doctor
|
|
13
14
|
```
|
|
14
15
|
|
|
@@ -44,7 +45,9 @@ Optional:
|
|
|
44
45
|
|
|
45
46
|
## Behavior
|
|
46
47
|
|
|
47
|
-
|
|
48
|
+
Start OpenCode as usual. The memory plugin needs no wrapper; optional
|
|
49
|
+
[agent recovery](../../docs/recovery.md) uses a separate configured wrapper.
|
|
50
|
+
The plugin:
|
|
48
51
|
|
|
49
52
|
1. Observes the first user prompt and stages scoped active context.
|
|
50
53
|
2. On session idle, stages the latest completed assistant response.
|
|
@@ -57,6 +60,62 @@ Enforce mode, the tool call is blocked when a required rule matches or the
|
|
|
57
60
|
verified saved policy cannot be retrieved (for example, during an outage);
|
|
58
61
|
the thrown error tells the agent how the user can approve.
|
|
59
62
|
|
|
60
|
-
Node.js 22 or newer is required.
|
|
61
|
-
[
|
|
62
|
-
|
|
63
|
+
Node.js 22 or newer is required. The complete connector surface is in
|
|
64
|
+
[Connect agents](../../docs/guides/getting-started.md#connect-agents).
|
|
65
|
+
|
|
66
|
+
## Review-first use
|
|
67
|
+
|
|
68
|
+
Start with one repository and real conventions you can verify. In Lore
|
|
69
|
+
**Settings**, set **Automatic learning mode** to **Proposal only** before
|
|
70
|
+
capturing corrections. Every automatic capture then waits for review, and
|
|
71
|
+
proposed learnings cannot be retrieved or injected. Manual learnings follow
|
|
72
|
+
the workspace's normal permissions and review requirements.
|
|
73
|
+
|
|
74
|
+
Use a dedicated connection for the machine so its token can be revoked
|
|
75
|
+
independently. Browser approval creates the token for you. A named manual token
|
|
76
|
+
from **Connect** remains available with `lore connect --token ... --agent opencode`;
|
|
77
|
+
keep its value out of agent prompts.
|
|
78
|
+
|
|
79
|
+
1. Start `opencode` in the repository and work normally. When correcting it,
|
|
80
|
+
state the durable rule and where it applies. For example: “Every new catalog
|
|
81
|
+
component needs a story file before merge. Keep that as this repository's
|
|
82
|
+
convention.” Avoid asking it to remember everything.
|
|
83
|
+
2. Open the proposal in **Learnings**. Inspect the original source, statement,
|
|
84
|
+
and scope. Exclude secrets and temporary task instructions.
|
|
85
|
+
3. Approve a useful proposal or decline it. A conflict may require replacing
|
|
86
|
+
the existing learning or keeping it instead. Keep both only when both
|
|
87
|
+
statements are valid in distinct scopes; narrow their scopes first. Broad
|
|
88
|
+
workspace proposals and promotions require an owner or admin.
|
|
89
|
+
4. Start a fresh OpenCode session and request related work without repeating
|
|
90
|
+
the rule. Inspect the `lore-opencode-plugin` delivery in **Activity**, or
|
|
91
|
+
follow the learning on **Connect**. A receipt proves delivery; inspect the
|
|
92
|
+
response separately to judge whether the model used it.
|
|
93
|
+
|
|
94
|
+
Before expanding use, check that source and scope are accurate, approved
|
|
95
|
+
learnings reach relevant fresh sessions, and unrelated, pending, rejected,
|
|
96
|
+
superseded, and forgotten learnings stay out of retrieval. Record missed
|
|
97
|
+
corrections, false captures, irrelevant deliveries, and review time. Keep
|
|
98
|
+
proposal-only mode until the review cost and capture quality are acceptable.
|
|
99
|
+
Optional LLM conflict analysis is advisory and never activates a proposal by
|
|
100
|
+
itself.
|
|
101
|
+
|
|
102
|
+
For a repeatable, credential-gated live check, see
|
|
103
|
+
[OpenCode acceptance](../../docs/guides/development.md#tests). The fixture-based
|
|
104
|
+
[first-learning journey](../../docs/product-verification.md#dashboard-journeys)
|
|
105
|
+
checks the dashboard flow without calling model providers.
|
|
106
|
+
|
|
107
|
+
## Disconnect
|
|
108
|
+
|
|
109
|
+
Use **Forget** to stop future retrieval of an active learning while retaining
|
|
110
|
+
history. Decline pending proposals that should never be used.
|
|
111
|
+
|
|
112
|
+
```sh
|
|
113
|
+
lore disconnect
|
|
114
|
+
lore status --json
|
|
115
|
+
```
|
|
116
|
+
|
|
117
|
+
Disconnect is machine-wide. It removes Lore-owned integrations and credentials,
|
|
118
|
+
preserves unrelated host configuration, and retains the Reliability v1 store
|
|
119
|
+
for acknowledged captures and invocation evidence. It does not delete
|
|
120
|
+
server-side learnings or receipts. Reconnect any other agents that should stay
|
|
121
|
+
connected, then revoke the old machine token in Lore.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lore-co/opencode",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.24",
|
|
4
4
|
"description": "Durable Lore context and capture integration for OpenCode",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "./dist/index.js",
|
|
@@ -34,10 +34,10 @@
|
|
|
34
34
|
},
|
|
35
35
|
"dependencies": {
|
|
36
36
|
"@opencode-ai/plugin": "^1.18.18",
|
|
37
|
-
"@lore-co/adapter-generic": "0.1.
|
|
38
|
-
"@lore-co/cli": "0.1.
|
|
39
|
-
"@lore-co/
|
|
40
|
-
"@lore-co/
|
|
37
|
+
"@lore-co/adapter-generic": "0.1.24",
|
|
38
|
+
"@lore-co/cli": "0.1.24",
|
|
39
|
+
"@lore-co/sdk": "0.1.24",
|
|
40
|
+
"@lore-co/core": "0.1.24"
|
|
41
41
|
},
|
|
42
42
|
"devDependencies": {
|
|
43
43
|
"@types/node": "^26.2.0",
|