@tanagram/lore 0.1.88 → 0.1.90
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 +49 -3
- package/dist/index.js +212 -211
- package/package.json +3 -3
- package/skills/lore-read/SKILL.md +16 -3
- package/skills/share/SKILL.md +40 -0
package/README.md
CHANGED
|
@@ -1,8 +1,54 @@
|
|
|
1
|
-
#
|
|
1
|
+
# Lore
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Lore captures your Claude Code, Codex, and Cowork sessions and turns them
|
|
4
|
+
into something your team can search, discuss, and build on.
|
|
4
5
|
|
|
5
|
-
|
|
6
|
+
Your AI coding sessions run on your machine. The Lore CLI watches for new
|
|
7
|
+
ones and uploads them to your workspace automatically, so there is no
|
|
8
|
+
copy-paste, no screenshots, no "save this thread" button to remember.
|
|
9
|
+
|
|
10
|
+
## Get started
|
|
11
|
+
|
|
12
|
+
```sh
|
|
13
|
+
npm install -g @tanagram/lore
|
|
14
|
+
lore
|
|
15
|
+
```
|
|
16
|
+
|
|
17
|
+
`lore` opens a dashboard in your terminal. Sign in there once and, on
|
|
18
|
+
macOS, background uploads start immediately. On Linux, run `lore configure`
|
|
19
|
+
to pick which directories upload.
|
|
20
|
+
|
|
21
|
+
That's it. Keep coding. New sessions show up in your workspace automatically.
|
|
22
|
+
|
|
23
|
+
## How privacy works
|
|
24
|
+
|
|
25
|
+
**Private by default.** Every session starts visible only to you. You
|
|
26
|
+
choose per session whether to share it with your workspace or make it
|
|
27
|
+
public. Workspace admins cannot override that choice.
|
|
28
|
+
|
|
29
|
+
**You control what uploads.** Lore only uploads sessions from directories
|
|
30
|
+
you allowlist. The first-run wizard pre-checks your three most recent
|
|
31
|
+
projects; nothing outside your allowlist is ever sent. Re-run the picker
|
|
32
|
+
any time with `lore configure`, or edit the list directly:
|
|
33
|
+
|
|
34
|
+
```sh
|
|
35
|
+
lore listen list # what's currently allowlisted
|
|
36
|
+
lore listen create ~/code/project # start uploading from here
|
|
37
|
+
lore listen delete ~/code/project # stop
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
**What a session contains.** Your prompts, the assistant's responses,
|
|
41
|
+
tool calls, file edits, and diffs, plus metadata like timestamps, model,
|
|
42
|
+
and the repo it ran in. Diffs include the changed lines of the files you
|
|
43
|
+
edited. Lore does not collect environment variables, secrets, or API keys.
|
|
44
|
+
|
|
45
|
+
**Stop anytime.** `lore disable` halts background uploads. `lore logout`
|
|
46
|
+
removes your stored credentials. You can delete any session, or your whole
|
|
47
|
+
account, from the web app.
|
|
48
|
+
|
|
49
|
+
---
|
|
50
|
+
|
|
51
|
+
## Reference: upload filters
|
|
6
52
|
|
|
7
53
|
The Lore daemon evaluates `~/.lore/upload_filters.json` (`~/.lore-dev/`
|
|
8
54
|
in dev) before auto-uploading Claude Code sessions. Missing config or an
|