@tanagram/lore 0.1.86 → 0.1.88

package/README.md

@@ -2,30 +2,30 @@
 
 The command-line interface for Lore.
 
-## Privacy: Lore only uploads from directories you allow
-
-By default the Lore daemon does **not** auto-upload any Claude Code
-session. You have to opt in per directory. This is the consent-first
-contract:
-
-- Sessions whose cwd is not under one of your upload directories are
-  ignored by the daemon — they stay on your machine.
-- The explicit commands (`lore export`, `lore share-codex`,
-  `lore share-cowork`) are user-initiated and bypass the upload-dir
-  gate. You can always opt-in per session.
-- The allowlist lives in `~/.lore/upload_dirs.json` (`~/.lore-dev/` in
-  dev), written with 0600 mode so other users on the same machine can't
-  read it.
-
-Adding directories takes a single keystroke on first login — the TUI
-shows your most-recent Claude Code project cwds with the top three
-pre-checked, and pressing Enter accepts them. `lore listen configure`
-re-enters that same interactive flow any time (it's also one of the
-quick actions on the `lore` dashboard). For scripted/non-interactive
-edits, manage the list directly:
+## Privacy: Lore uploads according to your local filters
+
+The Lore daemon evaluates `~/.lore/upload_filters.json` (`~/.lore-dev/`
+in dev) before auto-uploading Claude Code sessions. Missing config or an
+empty `include` allowlist means upload nothing. The `cwd` and `repo`
+allowlists are a union: a session is location-allowed if it matches a
+`cwd` rule OR a `repo` rule (so a non-git directory uploads via its `cwd`
+even when `repo` rules also exist). When set, `include.skills` further
+narrows that set (ANDed). Values within a dimension are ORed, and
+`exclude` rules override includes.
+
+The explicit commands (`lore export`, `lore share-codex`,
+`lore share-cowork`) are user-initiated and upload the requested session
+directly.
+
+Adding repos and directories through the TUI is a convenience for writing
+`repo` and `cwd` include filters. The post-login wizard shows your
+most-recent Claude Code projects with the top three pre-checked: a project
+inside a git repo is offered as its `origin` remote, and a non-repo
+directory is offered by its path. Pressing Enter accepts them. `lore configure` re-enters that same interactive flow any time
+(it's also one of the quick actions on the `lore` dashboard). For
+scripted/non-interactive edits, manage the cwd filters directly:
 
 ```sh
-lore listen configure                         # re-run the interactive wizard
 lore listen create ~/code/projectA            # watch ~/code/projectA
 lore listen create ~/work --workspace acme          # route work to a non-default workspace
 lore listen list                              # tabular output
@@ -34,7 +34,7 @@ lore listen update ~/work --workspace other-corp    # reassign workspace
 lore listen delete ~/code/projectA            # stop uploading from
 ```
 
-Matching uses path-separator-aware **prefix-tree** semantics, so adding
+`cwd` matching uses path-separator-aware **prefix-tree** semantics, so adding
 `~/code` covers `~/code/projectA`, `~/code/projectA/src`, etc., but
 deliberately does **not** cover `~/code-other`. The most-specific
 matching entry wins, so you can have a broad personal `~/` allow plus a
@@ -79,8 +79,8 @@ through Ink in TTY mode:
   device code panel → polling), then a success box with the resolved
   LaunchAgent paths. Distinct copy for timed-out / denied / expired.
   On first login the device-code flow is followed by a one-screen
-  "Configure upload directories" wizard so the daemon has explicit
-  consent to upload anything (see Privacy section above).
+  "Configure uploads" wizard that writes `repo` and `cwd` include
+  filters from your recent repos and directories.
 - **`lore enable` / `disable` / `restart`** — spinner with mode-specific
   copy while launchctl works, then a success or error MessageBox.
 - **`lore status`** — two-panel view (health on the left, paths on the
@@ -146,8 +146,8 @@ Esc to return to the sidebar, and q to exit.
 - `lore disable` — stops and removes the macOS background uploader.
 - `lore restart` — restarts the macOS background uploader.
 - `lore status` / `lore status --json` — shows background uploader health.
-- `lore listen configure` — re-enter the interactive wizard for picking
-  the directories Lore auto-uploads from (the same flow shown on first
+- `lore configure` — re-enter the interactive wizard for picking the
+  directories Lore auto-uploads from (the same flow shown on first
   login). Requires an interactive terminal.
 - `lore listen create <path> [--workspace <name>]` — allowlist a directory for
   daemon auto-uploads. Defaults to your active workspace; pass workspace
@@ -164,7 +164,9 @@ Esc to return to the sidebar, and q to exit.
   JSON object with the thread URL. Use `--session-id <id>` to pick a specific
   session, `--project <path>` to override the project lookup, and
   `--visibility private|workspace|public` to set the resulting thread's
-  visibility. The URL is also copied to the system clipboard when a clipboard
+  visibility. Use `--highlight <description>` to have the API resolve a
+  natural-language share highlight and return a `/thread/<id>#tb_…` block
+  anchor or range when it finds a match. The URL is also copied to the system clipboard when a clipboard
   tool is available (`pbcopy` / `wl-copy` / `xclip` / `xsel` / `clip.exe`).
 - `lore share-cowork` — shares a Claude Cowork local-agent-mode session
   to Lore. Defaults to the current session when run from inside one
@@ -174,7 +176,7 @@ Esc to return to the sidebar, and q to exit.
   Use `--session <session-id>` to share a specific session by id, or
   `--list` to enumerate local sessions newest-first without sharing.
   Re-running for the same session converges to the same thread (md5
-  dedup), so it's safe to retry. Prints the resulting `/session/<id>`
+  dedup), so it's safe to retry. Prints the resulting `/thread/<id>`
   URL on success.
 
 ## Dev vs prod