@tanagram/lore 0.1.163 → 0.1.165
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 +13 -9
- package/dist/index.js +240 -239
- package/package.json +4 -4
package/README.md
CHANGED
|
@@ -50,9 +50,9 @@ account, from the web app.
|
|
|
50
50
|
|
|
51
51
|
## Reference: upload filters
|
|
52
52
|
|
|
53
|
-
The Lore
|
|
54
|
-
in dev) before auto-uploading Claude Code sessions.
|
|
55
|
-
empty `include` allowlist means upload nothing. The `cwd` and `repo`
|
|
53
|
+
The Lore background agent evaluates `~/.lore/upload_filters.json`
|
|
54
|
+
(`~/.lore-dev/` in dev) before auto-uploading Claude Code sessions.
|
|
55
|
+
Missing config or an empty `include` allowlist means upload nothing. The `cwd` and `repo`
|
|
56
56
|
allowlists are a union: a session is location-allowed if it matches a
|
|
57
57
|
`cwd` rule OR a `repo` rule (so a non-git directory uploads via its `cwd`
|
|
58
58
|
even when `repo` rules also exist). When set, `include.skills` further
|
|
@@ -85,6 +85,10 @@ deliberately does **not** cover `~/code-other`. The most-specific
|
|
|
85
85
|
matching entry wins, so you can have a broad personal `~/` allow plus a
|
|
86
86
|
narrower `~/work` override that routes to a different org.
|
|
87
87
|
|
|
88
|
+
If a `cwd` include points at your entire home directory, `lore listen list`
|
|
89
|
+
prints a warning and suggests replacing it with narrower project paths. Lore
|
|
90
|
+
does not rewrite existing allowlists automatically.
|
|
91
|
+
|
|
88
92
|
## Interactive TUI
|
|
89
93
|
|
|
90
94
|
Running `lore` with no subcommand drops you into an interactive Ink
|
|
@@ -189,16 +193,16 @@ Esc to return to the sidebar, and q to exit.
|
|
|
189
193
|
- `lore version` — prints the CLI version.
|
|
190
194
|
- `lore update` — runs the same update check as the background auto-updater,
|
|
191
195
|
waits for it to finish, and prints the result.
|
|
192
|
-
- `lore enable` — installs and starts the macOS background
|
|
193
|
-
- `lore disable` — stops and removes the macOS background
|
|
194
|
-
- `lore restart` — restarts the macOS background
|
|
195
|
-
- `lore status` / `lore status --json` — shows background
|
|
196
|
+
- `lore enable` — installs and starts the macOS background agent.
|
|
197
|
+
- `lore disable` — stops and removes the macOS background agent.
|
|
198
|
+
- `lore restart` — restarts the macOS background agent.
|
|
199
|
+
- `lore status` / `lore status --json` — shows background-agent health and recent activity. The plain output does not treat an idle process as broken just because there is no active upload at that instant.
|
|
196
200
|
- `lore configure` — re-enter the interactive wizard for picking the
|
|
197
201
|
repos and directories Lore auto-uploads from (the same flow shown on first
|
|
198
202
|
login). Requires an interactive terminal.
|
|
199
|
-
- `lore listen create <path>` — allowlist a directory for
|
|
203
|
+
- `lore listen create <path>` — allowlist a directory for background auto-uploads.
|
|
200
204
|
- `lore listen list [--json]` — print the effective repo and cwd locations
|
|
201
|
-
the
|
|
205
|
+
the background agent may auto-upload from.
|
|
202
206
|
- `lore listen delete <path>` — stop uploading from a directory.
|
|
203
207
|
- `lore workspaces list` — calls `/api/whoami` and prints the WorkOS
|
|
204
208
|
workspaces the authenticated user currently belongs to. (Workspaces
|