@tanagram/lore 0.1.20 → 0.1.21
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 +6 -0
- package/dist/index.js +74 -74
- package/package.json +3 -3
- package/skills/lore-read/SKILL.md +1 -1
- package/skills/share/SKILL.md +3 -4
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@tanagram/lore",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.21",
|
|
4
4
|
"description": "Lore CLI",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|
|
@@ -21,8 +21,8 @@
|
|
|
21
21
|
"esbuild": "^0.24.0",
|
|
22
22
|
"tsx": "^4.20.6",
|
|
23
23
|
"typescript": "^5.9.3",
|
|
24
|
-
"@lore/
|
|
25
|
-
"@lore/
|
|
24
|
+
"@lore/transcripts": "0.1.0",
|
|
25
|
+
"@lore/contracts": "0.1.0"
|
|
26
26
|
},
|
|
27
27
|
"dependencies": {
|
|
28
28
|
"@sentry/node": "^10.47.0",
|
|
@@ -77,6 +77,6 @@ Both commands emit a single JSON object/array on stdout. After running:
|
|
|
77
77
|
|
|
78
78
|
## What This Does NOT Do
|
|
79
79
|
|
|
80
|
-
- It does not export the current session — that's the `share` skill (`
|
|
80
|
+
- It does not export the current session — that's the `share` skill (`lore export`).
|
|
81
81
|
- It does not modify threads, comments, visibility, or any Lore state. It is read-only.
|
|
82
82
|
- It does not start or manage the Lore background daemon.
|
package/skills/share/SKILL.md
CHANGED
|
@@ -27,7 +27,7 @@ Do NOT run this proactively. Only on explicit request.
|
|
|
27
27
|
Use this command as the default implementation:
|
|
28
28
|
|
|
29
29
|
```bash
|
|
30
|
-
|
|
30
|
+
lore export --session-id ${CLAUDE_SESSION_ID} --visibility workspace
|
|
31
31
|
```
|
|
32
32
|
|
|
33
33
|
Do **not** omit `--session-id` and rely on the cwd-match fallback. The fallback picks the most recent history entry for the current directory, which is frequently a *different* session (a prior run, a parallel worktree, etc.) — the user then has to retry with the explicit flag. The skill runtime gives you the session ID for free, so always pass it.
|
|
@@ -63,12 +63,11 @@ Echo the session URL back to the user as a clickable link. If `clipboard_copied`
|
|
|
63
63
|
|
|
64
64
|
## Failure Modes
|
|
65
65
|
|
|
66
|
-
- **Not logged in**: the command returns `not logged in — run '
|
|
66
|
+
- **Not logged in**: the command returns `not logged in — run 'lore login' first`. Tell the user to run `lore login` and try again.
|
|
67
67
|
- **No matching history entry**: this happens when `${CLAUDE_SESSION_ID}` isn't present in `~/.claude/history.jsonl` yet (very fresh session) or when the user asked to share a session that the CLI can't find. Ask the user which session they want to share, or suggest `--session-id <id>` / `--project <path>` with the value they provide.
|
|
68
|
-
- **Lore is offline locally**: the command suggests setting `TANAGRAM_LORE_URL` when the SaaS endpoint is unreachable. Relay the message verbatim.
|
|
69
68
|
|
|
70
69
|
## What This Does NOT Do
|
|
71
70
|
|
|
72
|
-
- It does not start the Lore background daemon. For ongoing auto-sync of every session, `
|
|
71
|
+
- It does not start the Lore background daemon. For ongoing auto-sync of every session, `lore enable` is the right command.
|
|
73
72
|
- It does not change the thread title, comments, or other metadata. The user can adjust those in the Lore UI after sharing.
|
|
74
73
|
- It does not advance the background daemon's sync cursor. If the daemon is running, it may re-upload the same session on its next cycle — Lore will return the same thread ID, so this is a no-op.
|