ghosttrap-cli 0.3.14__tar.gz → 0.3.15__tar.gz

{ghosttrap_cli-0.3.14 → ghosttrap_cli-0.3.15}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ghosttrap-cli
-Version: 0.3.14
+Version: 0.3.15
 Summary: Watch for errors streaming from ghosttrap.io
 Project-URL: Homepage, https://github.com/alex-rowley/ghosttrap-cli
 Requires-Python: >=3.10
@@ -56,10 +56,11 @@ Your app needs [ghosttrap-sdk](https://github.com/alex-rowley/ghosttrap-sdk) to
 
 ## How it works
 
-- **Setup** authenticates with GitHub to prove you own the repo, then saves a token locally
+- **Setup** authenticates with GitHub (via the active `gh` account) to prove you have access to the repo, then saves a repo token locally. If your active `gh` account can't see the repo, setup fails with a clear message; switch with `gh auth switch` and retry.
 - **Peek** and **watch** connect to ghosttrap.io using that token — no GitHub auth needed after setup
 - Errors that arrive while you're offline are replayed on next connect (cursor-based, no duplicates)
-- Local state is stored in `~/.ghosttrap/config.json`
+- Repos are tracked by GitHub's immutable repo id, so a rename or transfer doesn't require any action — the next connect picks up the new `owner/name` and your token keeps working
+- Local state is stored in `~/.ghosttrap/config.json`, keyed by GitHub repo id
 
 ## Requirements
 
@@ -70,4 +71,8 @@ Your app needs [ghosttrap-sdk](https://github.com/alex-rowley/ghosttrap-sdk) to
 
 ## Privacy
 
-Error data (tracebacks, exception messages, file paths) is routed through ghosttrap.io. The server is not open source yet — if there's demand for self-hosting, we'll open it up. Your GitHub token is used only during `setup` to verify repo ownership; it's never stored on the server. After setup, all communication uses a repo-specific token that grants access only to that repo's error stream — it cannot access your GitHub account.
+Error data (tracebacks, exception messages, file paths) is routed through ghosttrap.io. The server is not open source yet — if there's demand for self-hosting, we'll open it up. Your GitHub token is used only during `setup` to verify repo access; it's never stored on the server. After setup, all communication uses a repo-specific token that grants access only to that repo's error stream — it cannot access your GitHub account.
+
+User context (Django user id + username) is **never** sent unless you opt in with `ghosttrap.init(token, send_user=True)` in your app. Server hostname is captured automatically.
+
+Run `ghosttrap nuke` from inside a repo to permanently delete every server-side row for that repo (errors + the token itself). Requires typing the repo name to confirm.

{ghosttrap_cli-0.3.14 → ghosttrap_cli-0.3.15}/README.md

@@ -47,10 +47,11 @@ Your app needs [ghosttrap-sdk](https://github.com/alex-rowley/ghosttrap-sdk) to
 
 ## How it works
 
-- **Setup** authenticates with GitHub to prove you own the repo, then saves a token locally
+- **Setup** authenticates with GitHub (via the active `gh` account) to prove you have access to the repo, then saves a repo token locally. If your active `gh` account can't see the repo, setup fails with a clear message; switch with `gh auth switch` and retry.
 - **Peek** and **watch** connect to ghosttrap.io using that token — no GitHub auth needed after setup
 - Errors that arrive while you're offline are replayed on next connect (cursor-based, no duplicates)
-- Local state is stored in `~/.ghosttrap/config.json`
+- Repos are tracked by GitHub's immutable repo id, so a rename or transfer doesn't require any action — the next connect picks up the new `owner/name` and your token keeps working
+- Local state is stored in `~/.ghosttrap/config.json`, keyed by GitHub repo id
 
 ## Requirements
 
@@ -61,4 +62,8 @@ Your app needs [ghosttrap-sdk](https://github.com/alex-rowley/ghosttrap-sdk) to
 
 ## Privacy
 
-Error data (tracebacks, exception messages, file paths) is routed through ghosttrap.io. The server is not open source yet — if there's demand for self-hosting, we'll open it up. Your GitHub token is used only during `setup` to verify repo ownership; it's never stored on the server. After setup, all communication uses a repo-specific token that grants access only to that repo's error stream — it cannot access your GitHub account.
+Error data (tracebacks, exception messages, file paths) is routed through ghosttrap.io. The server is not open source yet — if there's demand for self-hosting, we'll open it up. Your GitHub token is used only during `setup` to verify repo access; it's never stored on the server. After setup, all communication uses a repo-specific token that grants access only to that repo's error stream — it cannot access your GitHub account.
+
+User context (Django user id + username) is **never** sent unless you opt in with `ghosttrap.init(token, send_user=True)` in your app. Server hostname is captured automatically.
+
+Run `ghosttrap nuke` from inside a repo to permanently delete every server-side row for that repo (errors + the token itself). Requires typing the repo name to confirm.

{ghosttrap_cli-0.3.14 → ghosttrap_cli-0.3.15}/ghosttrap_cli/cli.py

@@ -21,9 +21,10 @@ KNOWN_SKILL_HASHES = {
     "38810f43867a2a91420cc3dacbc71d2acabd7125596fd5b43f222b49725c9696",  # v0.3.10
     "19b67d913dc5214ee4db3610bd8749da67324c174b904b5da71ee6de13e23e63",  # v0.3.11
     "bf7768c3de266b7018d5c722c6c9991b487e7897786b3a406c460842cdcde8b5",  # v0.3.12
+    "d3f594c4c3601a4594c18ebc5e16dfd4abad4ab97d56285ecc20634b919b6731",  # v0.3.14
 }
 
-__version__ = "0.3.14"
+__version__ = "0.3.15"
 
 GHOSTTRAP_SERVER = "wss://ghosttrap.io/stream/"
 CONFIG_DIR = os.path.expanduser("~/.ghosttrap")
@@ -70,7 +71,7 @@ Read `~/.ghosttrap/config.json` for state. It contains:
 
 1. Detect the current repo from `git config --get remote.origin.url` (returns `owner/name`).
 2. Find a matching entry in config by looking for one whose `owner`/`name` equals the detected slug. If no match, tell the user to run `ghosttrap setup`. (The owner/name on a config entry auto-refreshes from the server when the repo is renamed or transferred, so always match against the entry's stored owner/name, not the config key.)
-3. If `sdk_installed` is false or missing: install the SDK (`pip install ghosttrap-sdk`), wire `ghosttrap.init("<token>")` into the app startup. For Django projects, also add `"ghosttrap.django.GhostTrapApp"` to INSTALLED_APPS (re-attaches logging handler after Django's dictConfig) and `"ghosttrap.django.GhostTrapMiddleware"` to MIDDLEWARE (catches unhandled view exceptions). The SDK auto-hooks into Celery task_failure if Celery is installed, and attaches a logging handler for logger.exception() calls. Use whatever pattern the project already uses for configuration (env vars, settings files, hardcoded — match the existing style). Then update the config: set `sdk_installed: true`, `sdk_version`, `init_file` to record what you did.
+3. If `sdk_installed` is false or missing: install the SDK (`pip install ghosttrap-sdk`), wire `ghosttrap.init("<token>")` into the app startup. For Django projects, also add `"ghosttrap.django.GhostTrapApp"` to INSTALLED_APPS (re-attaches logging handler after Django's dictConfig) and `"ghosttrap.django.GhostTrapMiddleware"` to MIDDLEWARE (catches unhandled view exceptions). The SDK auto-hooks into Celery task_failure if Celery is installed, and attaches a logging handler for logger.exception() calls. Use whatever pattern the project already uses for configuration (env vars, settings files, hardcoded — match the existing style). Then update the config: set `sdk_installed: true`, `sdk_version`, `init_file` to record what you did. Only pass `send_user=True` to `init()` if the user explicitly asks for user context in reports — it's PII and stays off by default.
 4. Run `ghosttrap peek --clear` with `run_in_background: true`. The `--clear` flag skips any stale backlog from prior sessions so you only get fresh errors.
 
 ## When peek returns

{ghosttrap_cli-0.3.14 → ghosttrap_cli-0.3.15}/ghosttrap_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ghosttrap-cli
-Version: 0.3.14
+Version: 0.3.15
 Summary: Watch for errors streaming from ghosttrap.io
 Project-URL: Homepage, https://github.com/alex-rowley/ghosttrap-cli
 Requires-Python: >=3.10
@@ -56,10 +56,11 @@ Your app needs [ghosttrap-sdk](https://github.com/alex-rowley/ghosttrap-sdk) to
 
 ## How it works
 
-- **Setup** authenticates with GitHub to prove you own the repo, then saves a token locally
+- **Setup** authenticates with GitHub (via the active `gh` account) to prove you have access to the repo, then saves a repo token locally. If your active `gh` account can't see the repo, setup fails with a clear message; switch with `gh auth switch` and retry.
 - **Peek** and **watch** connect to ghosttrap.io using that token — no GitHub auth needed after setup
 - Errors that arrive while you're offline are replayed on next connect (cursor-based, no duplicates)
-- Local state is stored in `~/.ghosttrap/config.json`
+- Repos are tracked by GitHub's immutable repo id, so a rename or transfer doesn't require any action — the next connect picks up the new `owner/name` and your token keeps working
+- Local state is stored in `~/.ghosttrap/config.json`, keyed by GitHub repo id
 
 ## Requirements
 
@@ -70,4 +71,8 @@ Your app needs [ghosttrap-sdk](https://github.com/alex-rowley/ghosttrap-sdk) to
 
 ## Privacy
 
-Error data (tracebacks, exception messages, file paths) is routed through ghosttrap.io. The server is not open source yet — if there's demand for self-hosting, we'll open it up. Your GitHub token is used only during `setup` to verify repo ownership; it's never stored on the server. After setup, all communication uses a repo-specific token that grants access only to that repo's error stream — it cannot access your GitHub account.
+Error data (tracebacks, exception messages, file paths) is routed through ghosttrap.io. The server is not open source yet — if there's demand for self-hosting, we'll open it up. Your GitHub token is used only during `setup` to verify repo access; it's never stored on the server. After setup, all communication uses a repo-specific token that grants access only to that repo's error stream — it cannot access your GitHub account.
+
+User context (Django user id + username) is **never** sent unless you opt in with `ghosttrap.init(token, send_user=True)` in your app. Server hostname is captured automatically.
+
+Run `ghosttrap nuke` from inside a repo to permanently delete every server-side row for that repo (errors + the token itself). Requires typing the repo name to confirm.

{ghosttrap_cli-0.3.14 → ghosttrap_cli-0.3.15}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "ghosttrap-cli"
-version = "0.3.14"
+version = "0.3.15"
 description = "Watch for errors streaming from ghosttrap.io"
 readme = "README.md"
 requires-python = ">=3.10"