@lore-co/cli 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 CHANGED
@@ -1,33 +1,26 @@
1
1
  # Lore CLI
2
2
 
3
- The Lore connector installs native Codex and Claude Code lifecycle hooks. Every
4
- prompt retrieves relevant engineering context. A first prompt is observed on
5
- its own; later prompts are paired with the previous assistant response so Lore
6
- can capture explicit corrections.
3
+ The Lore connector installs native Codex and Claude Code lifecycle hooks. For
4
+ each supported prompt, Lore attempts to retrieve relevant engineering context.
5
+ A first prompt is observed on its own; later prompts are paired with the
6
+ previous assistant response when valid pending state is available. Hook and
7
+ network failures fail open so they do not block the agent.
7
8
 
8
- ## Connect
9
+ ## Install and connect
9
10
 
10
11
  ```sh
11
- curl -fsSL https://raw.githubusercontent.com/treadiehq/lore/main/scripts/install.sh | bash
12
+ pnpm install --global @lore-co/cli
13
+
12
14
  lore connect \
13
15
  --url https://lore.example.com \
14
- --token "$LORE_TOKEN"
15
- ```
16
-
17
- The standalone binary supports macOS and Linux on x64 and arm64. Downloads are
18
- verified against the release SHA-256 manifest and do not require a JavaScript
19
- runtime. Use `lore update` to install a newer release.
20
-
21
- The npm package remains available for JavaScript-based environments:
16
+ --token "$LORE_WORKSPACE_TOKEN" \
17
+ --agent claude \
18
+ --agent codex
22
19
 
23
- ```sh
24
- npx @lore-co/cli connect \
25
- --url https://lore.example.com \
26
- --token "$LORE_TOKEN"
20
+ lore doctor
27
21
  ```
28
22
 
29
- Only the npm package scope is `@lore-co`; the installed executable and every
30
- command remain `lore`.
23
+ The package requires Node.js 22 or newer and installs the `lore` command.
31
24
 
32
25
  `connect` auto-detects `codex` and `claude`. Use `--agent codex` or
33
26
  `--agent claude` for an explicit headless install. Configuration is stored in
@@ -46,7 +39,7 @@ lore doctor
46
39
  lore disconnect
47
40
  ```
48
41
 
49
- All commands also support `--json`. `disconnect` removes only hook handlers
42
+ The three commands above also support `--json`. `disconnect` removes only hook handlers
50
43
  marked as Lore-owned, then deletes Lore's credential, legacy hook runtime,
51
44
  pending state, and retry queue. It does not remove the installed `lore` binary
52
45
  or restore a whole backup over newer agent settings.
@@ -78,7 +71,7 @@ deliveries are visible through Lore activity.
78
71
  strict audited endpoints:
79
72
 
80
73
  ```sh
81
- LORE_API_URL=http://localhost:3004 \
74
+ LORE_API_URL=https://lore.example.com \
82
75
  LORE_WORKSPACE_TOKEN=... \
83
76
  lore host deliver --input delivery.json --output prompt
84
77
 
@@ -126,6 +119,12 @@ DEVIN_API_KEY=... DEVIN_ORG_ID=... \
126
119
  --prompt "Apply the reviewer correction"
127
120
  ```
128
121
 
122
+ The Lore API must also have Devin polling enabled with the same
123
+ `DEVIN_API_KEY` and `DEVIN_ORG_ID`, and the repository must appear in
124
+ `DEVIN_REPOSITORY_ALLOWLIST`. `lore devin setup` checks Devin access and Lore
125
+ reachability; `start` performs authenticated delivery and poller-registration
126
+ checks.
127
+
129
128
  Both commands retrieve Lore context with a stable delivery event and receipt.
130
129
  `devin start` registers the created session for transcript polling.
131
130
  `devin prompt` re-registers the session before sending, so a paused poller can
@@ -154,26 +153,29 @@ OPENAI_API_KEY=... DEVIN_API_KEY=... DEVIN_ORG_ID=org-... \
154
153
  --configure-secrets
155
154
  ```
156
155
 
157
- The installer copies trusted workflow and output-schema templates without
158
- committing them. Codex uses the official Codex action. Devin uses a normal v3
159
- session because the dedicated Devin Review API cannot accept dynamic Lore
160
- context. Reviews run only for same-repository, non-draft pull requests bearing
161
- the corresponding `lore:codex-review` or `lore:devin-review` label.
156
+ The command overwrites three fixed Lore workflow files and the Lore review
157
+ schema without committing them. Review or back up existing files first.
158
+ `--configure-secrets` requires authenticated `gh` access and updates the named
159
+ Actions secrets and variables in the target repository. Codex uses the
160
+ official Codex action. Devin uses a normal v3 session because the dedicated
161
+ Devin Review API cannot accept dynamic Lore context. Reviews run only for
162
+ same-repository, non-draft pull requests bearing the corresponding
163
+ `lore:codex-review` or `lore:devin-review` label.
162
164
 
163
- Generated jobs download a pinned standalone release. Set repository variable
164
- `LORE_CLI_VERSION` to the release tag and, when using a fork, set
165
- `LORE_CLI_REPOSITORY` to its `owner/repository` value. The installer verifies
166
- the downloaded binary before each job invokes `lore` directly.
165
+ Generated jobs require a published standalone binary release. No public binary
166
+ release exists yet, so the generated defaults cannot currently install Lore.
167
+ After release, set `LORE_CLI_REPOSITORY` to its publicly readable
168
+ `owner/repository` and `LORE_CLI_VERSION` to an existing release tag.
167
169
 
168
170
  The workflows require secret `LORE_WORKSPACE_TOKEN` and variable
169
171
  `LORE_API_URL`. Codex additionally requires secret `OPENAI_API_KEY`. Devin
170
172
  additionally requires secret `DEVIN_API_KEY` and variable `DEVIN_ORG_ID`.
171
- Review jobs use `contents: read` plus `pull-requests: write` so the workflow
172
- token can inspect and publish PR comments; the correction workflow has
173
- read-only GitHub permissions.
173
+ Codex separates a read-only review job from its `pull-requests: write` posting
174
+ job. The Devin review job uses `contents: read` and `pull-requests: write`.
175
+ The correction workflow has read-only GitHub permissions.
174
176
  Native `/devin review` cannot accept dynamic Lore context; the generated Lore
175
- workflow uses a normal capped Devin session instead. The optional managed
176
- plugin remains a closed-beta path controlled by Devin availability.
177
+ workflow uses a normal capped Devin session instead. The private Devin hook
178
+ prototype is not currently an installable managed plugin.
177
179
 
178
180
  An authorized maintainer can turn a false-positive bot comment into shared
179
181
  knowledge with:
@@ -184,35 +186,14 @@ knowledge with:
184
186
  The correction and current behavior go here.
185
187
  ```
186
188
 
187
- ## Release acceptance
189
+ ## Production guidance
188
190
 
189
- From the repository root, deterministic unit/integration checks, browser
190
- acceptance, and package-consumer smoke are:
191
-
192
- ```sh
193
- pnpm test
194
- pnpm typecheck
195
- pnpm build
196
- pnpm test:browser
197
- pnpm test:pack
198
- pnpm build:binary
199
- pnpm test:binary
200
- ```
201
-
202
- Credential-gated live commands are explicit and separate:
203
-
204
- ```sh
205
- RUN_NATIVE_AGENT_LIVE_TESTS=1 pnpm test:agents:live
206
- RUN_DEVIN_LIVE_TESTS=1 pnpm test:devin:live
207
- RUN_THREE_AGENT_CHAIN_LIVE_TESTS=RUN pnpm test:chain:live
208
- RUN_GITHUB_PR_LIVE_TESTS=1 pnpm test:github:live
209
- ```
191
+ - Use a dedicated workspace token for each person, machine, or integration.
192
+ - Connect only to an HTTPS Lore API outside local development.
193
+ - Run `lore doctor` after installation and configuration changes.
194
+ - Keep provider credentials in environment variables or GitHub Actions secrets.
195
+ - After standalone publication, pin `LORE_CLI_VERSION` in automated workflows
196
+ and update it deliberately.
210
197
 
211
- The native command covers first prompts and real resumed later turns in both
212
- Claude and Codex. The chain command covers Claude → Devin → fresh Codex and
213
- Claude. Both paths, plus standalone Devin acceptance, have passed with real
214
- authenticated clients. Both GitHub review/correction paths passed target
215
- preflight and exact-head acceptance with a packed current artifact on August
216
- 13, 2026. The current acceptance gate preflights a published standalone release.
217
- Rerun all live gates with customer credentials before rollout.
218
- Lore has no dream mode or company-wide search.
198
+ For source builds, self-hosting, tests, and release internals, see the
199
+ [technical and development guide](../../docs/detailed.md).
package/dist/runtime.js CHANGED
@@ -7,7 +7,7 @@ import { pathToFileURL } from "node:url";
7
7
  import { repositoryScopeFromGitRoot } from "./repository.js";
8
8
  const RUNTIME_VERSION = typeof __LORE_VERSION__ === "string" && __LORE_VERSION__ !== ""
9
9
  ? __LORE_VERSION__
10
- : "0.1.0";
10
+ : "0.1.1";
11
11
  const IS_STANDALONE_RUNTIME = typeof __LORE_STANDALONE__ === "boolean" && __LORE_STANDALONE__;
12
12
  const MAX_STDIN_BYTES = 1024 * 1024;
13
13
  const MAX_CONTEXT_CHARS = 12_000;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lore-co/cli",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "description": "Connect Codex and Claude Code to Lore shared engineering memory",
5
5
  "type": "module",
6
6
  "main": "./dist/index.js",
@@ -34,8 +34,8 @@
34
34
  "license": "FSL-1.1-MIT",
35
35
  "dependencies": {
36
36
  "zod": "^4.4.3",
37
- "@lore-co/core": "0.1.0",
38
- "@lore-co/sdk": "0.1.0"
37
+ "@lore-co/core": "0.1.1",
38
+ "@lore-co/sdk": "0.1.1"
39
39
  },
40
40
  "scripts": {
41
41
  "dev": "tsx watch src/cli.ts",