openlynx 0.2.0__py3-none-any.whl

lynx_memory/__init__.py

@@ -0,0 +1 @@
+__version__ = "0.2.0"

lynx_memory/assets/commands/lynx-memory-delete.md

@@ -0,0 +1,56 @@
+---
+description: Permanently delete lynx-memory history (requires double confirmation)
+allowed-tools: Bash(lynx-memory:*)
+---
+
+You are helping the user **permanently delete** lynx-memory history (sqlite + chroma vector store). This is irreversible. Follow the steps below strictly.
+
+## Step 1: Check current status
+
+```bash
+lynx-memory status
+```
+
+Report to the user: whether the project repo `./.lynx-memory/` and the global repo `~/.claude/lynx-memory/` exist, and the turn / summary counts of each.
+
+## Step 2: Ask which scope to delete
+
+Give the user three explicit options and ask them to pick one:
+
+- `project` — delete only the current project's memory
+- `global` — delete only the global memory
+- `both` — delete both
+
+## Step 3: First confirmation
+
+Restate the directory paths and counts that will be deleted, then ask: "Confirm deletion? Reply `DELETE` to continue."
+
+- The user must reply with the **exact English word `DELETE`** to pass the first confirmation.
+- Any other reply means abort — stop immediately and tell the user it has been cancelled.
+
+## Step 4: Second confirmation
+
+After the first one passes, ask again: "Final confirmation: are you sure you want to permanently delete all memory for [scope]? (y/N)"
+
+- The user must explicitly reply `y` or `yes`.
+- Any other reply means abort — stop immediately and tell the user it has been cancelled.
+
+## Step 5: Run the delete
+
+Only after both confirmations pass:
+
+```bash
+lynx-memory delete --scope <project|global|both> --yes
+```
+
+(`--yes` is used because the double confirmation has already happened in chat; the CLI's own interactive prompt can be skipped.)
+
+## Step 6: Check status after deletion
+
+```bash
+lynx-memory status
+```
+
+Report the change to the user.
+
+$ARGUMENTS

lynx_memory/assets/commands/lynx-memory-history.md

@@ -0,0 +1,31 @@
+---
+description: Open the local Web UI to browse project / global lynx-memory history
+allowed-tools: Bash(lynx-memory:*)
+---
+
+Start the local Web UI:
+
+```bash
+lynx-memory web
+```
+
+This will:
+
+- Start a FastAPI server on `127.0.0.1` on a free port
+- Open the UI in the system default browser (use `lynx-memory web --no-open` to skip)
+- Let the user paginate, run keyword / semantic search, delete single turns, and tag turns
+- Provide a scope toggle at the top of the page to switch between project and global history
+
+Remind the user:
+
+- Stop the server with `Ctrl+C`
+- The server only listens on `127.0.0.1`; it is not exposed externally
+- Default port is `9527`; override with `lynx-memory web --port 8080`, or `--port 0` to let the OS pick a free port
+
+UI delete and tag actions write to the database immediately:
+
+- Delete: `DELETE /api/turns/{scope}/{id}` → removes the row from SQLite `turns` / `turn_tags` and clears the Chroma vector
+- Tag: `POST /api/turns/{scope}/{id}/tags` → writes to `tags` / `turn_tags`
+- Untag: `DELETE /api/turns/{scope}/{id}/tags/{name}` → clears `turn_tags`, then clears `tags` if no other turn uses it
+
+Whatever the user does in the UI is the final state; no extra database commands are needed to sync.

lynx_memory/assets/commands/lynx-memory-pull-global.md

@@ -0,0 +1,40 @@
+---
+description: Merge global history into the current project (global → project)
+allowed-tools: Bash(lynx-memory:*)
+---
+
+You are helping the user merge the **global** lynx-memory repo into the **current project** repo.
+
+## Step 1: Check status before merging
+
+```bash
+lynx-memory status
+```
+
+Report the current scope, whether the project and global repos exist, and the turn / summary counts of each.
+
+## Step 2: Dry-run preview
+
+```bash
+lynx-memory merge --from global --to project --dry-run
+```
+
+Tell the user how many entries will be copied and get confirmation before continuing.
+
+## Step 3: Run the merge
+
+```bash
+lynx-memory merge --from global --to project
+```
+
+**Do not pass `--delete-source` by default.** Only append `--delete-source` if the user explicitly asks to wipe the source repo, and confirm again — this is destructive.
+
+## Step 4: Check status after merging
+
+```bash
+lynx-memory status
+```
+
+Show the user the change in counts.
+
+$ARGUMENTS

lynx_memory/assets/commands/lynx-memory-push-global.md

@@ -0,0 +1,40 @@
+---
+description: Merge the current project's history into the global repo (project → global)
+allowed-tools: Bash(lynx-memory:*)
+---
+
+You are helping the user merge the **current project** lynx-memory repo into the **global** repo.
+
+## Step 1: Check status before merging
+
+```bash
+lynx-memory status
+```
+
+Report the current scope, whether the project and global repos exist, and the turn / summary counts of each.
+
+## Step 2: Dry-run preview
+
+```bash
+lynx-memory merge --from project --to global --dry-run
+```
+
+Tell the user how many entries will be copied and get confirmation before continuing.
+
+## Step 3: Run the merge
+
+```bash
+lynx-memory merge --from project --to global
+```
+
+**Do not pass `--delete-source` by default.** Only append `--delete-source` if the user explicitly asks to wipe the source repo, and confirm again — this is destructive.
+
+## Step 4: Check status after merging
+
+```bash
+lynx-memory status
+```
+
+Show the user the change in counts.
+
+$ARGUMENTS

lynx_memory/assets/commands/lynx-memory-status.md

@@ -0,0 +1,20 @@
+---
+description: Show the current lynx-memory scope (project / global) and stats
+allowed-tools: Bash(lynx-memory:*)
+---
+
+Run:
+
+```bash
+lynx-memory status
+```
+
+Summarize the key points for the user:
+
+- **Current scope**: `project` or `global`
+- Path of the **active data directory**
+- Number of sessions / turns / summaries
+- Whether a project-level repo `./.lynx-memory/` exists in the current directory
+- Whether the global repo `~/.claude/lynx-memory/` exists
+
+Do not perform any write or merge operations.