claude-jacked 0.2.1__tar.gz → 0.2.2__tar.gz

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.
Files changed (32) hide show
  1. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/PKG-INFO +64 -17
  2. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/README.md +63 -16
  3. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/pyproject.toml +1 -1
  4. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/.claude/settings.local.json +0 -0
  5. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/.github/workflows/publish.yml +0 -0
  6. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/.gitignore +0 -0
  7. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/LICENSE +0 -0
  8. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/agents/code-simplicity-reviewer.md +0 -0
  9. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/agents/defensive-error-handler.md +0 -0
  10. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/agents/double-check-reviewer.md +0 -0
  11. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/agents/git-pr-workflow-manager.md +0 -0
  12. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/agents/issue-pr-coordinator.md +0 -0
  13. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/agents/pr-workflow-checker.md +0 -0
  14. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/agents/readme-maintainer.md +0 -0
  15. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/agents/test-coverage-engineer.md +0 -0
  16. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/agents/test-coverage-improver.md +0 -0
  17. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/agents/wiki-documentation-architect.md +0 -0
  18. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/commands/dc.md +0 -0
  19. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/commands/pr.md +0 -0
  20. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/docs/DESIGN.md +0 -0
  21. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/jacked/__init__.py +0 -0
  22. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/jacked/cli.py +0 -0
  23. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/jacked/client.py +0 -0
  24. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/jacked/config.py +0 -0
  25. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/jacked/indexer.py +0 -0
  26. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/jacked/retriever.py +0 -0
  27. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/jacked/searcher.py +0 -0
  28. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/jacked/transcript.py +0 -0
  29. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/skills/jacked/SKILL.md +0 -0
  30. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/tests/__init__.py +0 -0
  31. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/tests/test_config.py +0 -0
  32. {claude_jacked-0.2.1 → claude_jacked-0.2.2}/tests/test_transcript.py +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: claude-jacked
3
- Version: 0.2.1
3
+ Version: 0.2.2
4
4
  Summary: Cross-machine semantic search for Claude Code sessions
5
5
  Project-URL: Homepage, https://github.com/jackneil/claude-jacked
6
6
  Project-URL: Repository, https://github.com/jackneil/claude-jacked
@@ -33,23 +33,37 @@ Supercharge your Claude Code workflow with cross-machine session search, review
33
33
  ## Install (Copy This Into Claude Code)
34
34
 
35
35
  ```
36
- Install claude-jacked for me. First detect my OS, then guide me through the full setup:
37
-
38
- 1. Detect my operating system
39
- 2. Check if I have Python 3.11+. If not, help me install miniconda and create a Python 3.11 environment.
40
- 3. Check if I have pipx, install it if not (use Python 3.11)
41
- 4. Run: pipx install claude-jacked
42
- 5. Help me set up Qdrant Cloud (walk me through creating account at cloud.qdrant.io, getting credentials)
43
- 6. Help me add environment variables to my shell profile:
44
- - QDRANT_CLAUDE_SESSIONS_ENDPOINT (required)
45
- - QDRANT_CLAUDE_SESSIONS_API_KEY (required)
46
- - JACKED_USER_NAME (ask me what name I want to use for attribution)
47
- 7. Run: jacked install
48
- 8. Run: jacked backfill
49
- 9. Verify with: jacked status && jacked configure --show
50
-
51
- Ask me if I'm setting this up for personal use or for a team sharing sessions.
36
+ Install claude-jacked for me. First check what's already set up, then help me with anything missing:
37
+
38
+ DIAGNOSTIC PHASE (run these first to see current state):
39
+ - Detect my operating system
40
+ - Check if pipx is installed: pipx --version
41
+ - Check if jacked CLI is installed: jacked --version (or on Windows: where jacked)
42
+ - Check if Qdrant credentials are set: echo $QDRANT_CLAUDE_SESSIONS_ENDPOINT (bash) or echo %QDRANT_CLAUDE_SESSIONS_ENDPOINT% (cmd)
43
+ - Check current config: jacked configure --show (if jacked exists)
44
+ - Check if hook is installed: look in ~/.claude/settings.json for "jacked index"
45
+ - Check indexed sessions: jacked status (if connected)
46
+
47
+ REPORT what's already configured vs what's missing before proceeding.
48
+
49
+ SETUP PHASE (only do steps that are missing):
50
+ 1. If no Python 3.11+: help install miniconda
51
+ 2. If no pipx: pip install pipx && pipx ensurepath
52
+ 3. If jacked not installed: pipx install claude-jacked
53
+ 4. If no Qdrant credentials: walk me through cloud.qdrant.io setup
54
+ 5. If env vars missing: help add to shell profile (QDRANT_CLAUDE_SESSIONS_ENDPOINT, QDRANT_CLAUDE_SESSIONS_API_KEY, JACKED_USER_NAME)
55
+ 6. If hook/agents not installed: jacked install
56
+ 7. If no indexed sessions: jacked backfill
57
+
58
+ VERIFY: jacked status && jacked configure --show
59
+
60
+ Ask if this is personal use or team setup.
52
61
  If team: explain that everyone needs the same Qdrant cluster credentials.
62
+
63
+ WINDOWS NOTES:
64
+ - pipx installs jacked to: C:\Users\<user>\pipx\venvs\claude-jacked\Scripts\jacked.exe
65
+ - If "jacked" isn't found, find it with: where jacked OR dir C:\Users\%USERNAME%\pipx\venvs\claude-jacked\Scripts\jacked.exe
66
+ - In Git Bash, backslash paths get mangled. Use: cmd.exe /c "C:\full\path\to\jacked.exe <command>"
53
67
  ```
54
68
 
55
69
  ---
@@ -396,6 +410,39 @@ pipx install claude-jacked
396
410
 
397
411
  This installs globally so the hook can find it regardless of which env is active.
398
412
 
413
+ ### Windows: Path Issues in Git Bash
414
+
415
+ Claude Code uses Git Bash on Windows, which mangles backslash paths. When you run `C:\Users\jack\.local\bin\jacked.exe`, bash turns it into garbage like `C:Usersjack.localbinjacked.exe`.
416
+
417
+ **Where pipx installs jacked on Windows:**
418
+ ```
419
+ C:\Users\<your-username>\pipx\venvs\claude-jacked\Scripts\jacked.exe
420
+ ```
421
+
422
+ **Solutions:**
423
+
424
+ 1. **Use cmd.exe wrapper** (most reliable in Git Bash):
425
+ ```bash
426
+ cmd.exe /c "C:\Users\jack\pipx\venvs\claude-jacked\Scripts\jacked.exe status"
427
+ ```
428
+
429
+ 2. **Add Scripts folder to PATH** (one-time fix):
430
+ Add `C:\Users\<you>\pipx\venvs\claude-jacked\Scripts` to your Windows PATH environment variable.
431
+
432
+ 3. **Use forward slashes** (sometimes works):
433
+ ```bash
434
+ /c/Users/jack/pipx/venvs/claude-jacked/Scripts/jacked.exe status
435
+ ```
436
+
437
+ **Finding where jacked is installed:**
438
+ ```cmd
439
+ where jacked
440
+ ```
441
+ or
442
+ ```cmd
443
+ dir C:\Users\%USERNAME%\pipx\venvs\claude-jacked\Scripts\jacked.exe
444
+ ```
445
+
399
446
  ### Agents not loading
400
447
 
401
448
  Make sure files are in the right place:
@@ -5,23 +5,37 @@ Supercharge your Claude Code workflow with cross-machine session search, review
5
5
  ## Install (Copy This Into Claude Code)
6
6
 
7
7
  ```
8
- Install claude-jacked for me. First detect my OS, then guide me through the full setup:
9
-
10
- 1. Detect my operating system
11
- 2. Check if I have Python 3.11+. If not, help me install miniconda and create a Python 3.11 environment.
12
- 3. Check if I have pipx, install it if not (use Python 3.11)
13
- 4. Run: pipx install claude-jacked
14
- 5. Help me set up Qdrant Cloud (walk me through creating account at cloud.qdrant.io, getting credentials)
15
- 6. Help me add environment variables to my shell profile:
16
- - QDRANT_CLAUDE_SESSIONS_ENDPOINT (required)
17
- - QDRANT_CLAUDE_SESSIONS_API_KEY (required)
18
- - JACKED_USER_NAME (ask me what name I want to use for attribution)
19
- 7. Run: jacked install
20
- 8. Run: jacked backfill
21
- 9. Verify with: jacked status && jacked configure --show
22
-
23
- Ask me if I'm setting this up for personal use or for a team sharing sessions.
8
+ Install claude-jacked for me. First check what's already set up, then help me with anything missing:
9
+
10
+ DIAGNOSTIC PHASE (run these first to see current state):
11
+ - Detect my operating system
12
+ - Check if pipx is installed: pipx --version
13
+ - Check if jacked CLI is installed: jacked --version (or on Windows: where jacked)
14
+ - Check if Qdrant credentials are set: echo $QDRANT_CLAUDE_SESSIONS_ENDPOINT (bash) or echo %QDRANT_CLAUDE_SESSIONS_ENDPOINT% (cmd)
15
+ - Check current config: jacked configure --show (if jacked exists)
16
+ - Check if hook is installed: look in ~/.claude/settings.json for "jacked index"
17
+ - Check indexed sessions: jacked status (if connected)
18
+
19
+ REPORT what's already configured vs what's missing before proceeding.
20
+
21
+ SETUP PHASE (only do steps that are missing):
22
+ 1. If no Python 3.11+: help install miniconda
23
+ 2. If no pipx: pip install pipx && pipx ensurepath
24
+ 3. If jacked not installed: pipx install claude-jacked
25
+ 4. If no Qdrant credentials: walk me through cloud.qdrant.io setup
26
+ 5. If env vars missing: help add to shell profile (QDRANT_CLAUDE_SESSIONS_ENDPOINT, QDRANT_CLAUDE_SESSIONS_API_KEY, JACKED_USER_NAME)
27
+ 6. If hook/agents not installed: jacked install
28
+ 7. If no indexed sessions: jacked backfill
29
+
30
+ VERIFY: jacked status && jacked configure --show
31
+
32
+ Ask if this is personal use or team setup.
24
33
  If team: explain that everyone needs the same Qdrant cluster credentials.
34
+
35
+ WINDOWS NOTES:
36
+ - pipx installs jacked to: C:\Users\<user>\pipx\venvs\claude-jacked\Scripts\jacked.exe
37
+ - If "jacked" isn't found, find it with: where jacked OR dir C:\Users\%USERNAME%\pipx\venvs\claude-jacked\Scripts\jacked.exe
38
+ - In Git Bash, backslash paths get mangled. Use: cmd.exe /c "C:\full\path\to\jacked.exe <command>"
25
39
  ```
26
40
 
27
41
  ---
@@ -368,6 +382,39 @@ pipx install claude-jacked
368
382
 
369
383
  This installs globally so the hook can find it regardless of which env is active.
370
384
 
385
+ ### Windows: Path Issues in Git Bash
386
+
387
+ Claude Code uses Git Bash on Windows, which mangles backslash paths. When you run `C:\Users\jack\.local\bin\jacked.exe`, bash turns it into garbage like `C:Usersjack.localbinjacked.exe`.
388
+
389
+ **Where pipx installs jacked on Windows:**
390
+ ```
391
+ C:\Users\<your-username>\pipx\venvs\claude-jacked\Scripts\jacked.exe
392
+ ```
393
+
394
+ **Solutions:**
395
+
396
+ 1. **Use cmd.exe wrapper** (most reliable in Git Bash):
397
+ ```bash
398
+ cmd.exe /c "C:\Users\jack\pipx\venvs\claude-jacked\Scripts\jacked.exe status"
399
+ ```
400
+
401
+ 2. **Add Scripts folder to PATH** (one-time fix):
402
+ Add `C:\Users\<you>\pipx\venvs\claude-jacked\Scripts` to your Windows PATH environment variable.
403
+
404
+ 3. **Use forward slashes** (sometimes works):
405
+ ```bash
406
+ /c/Users/jack/pipx/venvs/claude-jacked/Scripts/jacked.exe status
407
+ ```
408
+
409
+ **Finding where jacked is installed:**
410
+ ```cmd
411
+ where jacked
412
+ ```
413
+ or
414
+ ```cmd
415
+ dir C:\Users\%USERNAME%\pipx\venvs\claude-jacked\Scripts\jacked.exe
416
+ ```
417
+
371
418
  ### Agents not loading
372
419
 
373
420
  Make sure files are in the right place:
@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
4
4
 
5
5
  [project]
6
6
  name = "claude-jacked"
7
- version = "0.2.1"
7
+ version = "0.2.2"
8
8
  description = "Cross-machine semantic search for Claude Code sessions"
9
9
  readme = "README.md"
10
10
  license = "MIT"
File without changes
File without changes