claude-jacked 0.2.2

Cross-machine semantic search for Claude Code sessions

claude-jacked

Supercharge your Claude Code workflow with cross-machine session search, review agents, and workflow commands.

Install (Copy This Into Claude Code)

Install claude-jacked for me. First check what's already set up, then help me with anything missing:

DIAGNOSTIC PHASE (run these first to see current state):
- Detect my operating system
- Check if pipx is installed: pipx --version
- Check if jacked CLI is installed: jacked --version (or on Windows: where jacked)
- Check if Qdrant credentials are set: echo $QDRANT_CLAUDE_SESSIONS_ENDPOINT (bash) or echo %QDRANT_CLAUDE_SESSIONS_ENDPOINT% (cmd)
- Check current config: jacked configure --show (if jacked exists)
- Check if hook is installed: look in ~/.claude/settings.json for "jacked index"
- Check indexed sessions: jacked status (if connected)

REPORT what's already configured vs what's missing before proceeding.

SETUP PHASE (only do steps that are missing):
1. If no Python 3.11+: help install miniconda
2. If no pipx: pip install pipx && pipx ensurepath
3. If jacked not installed: pipx install claude-jacked
4. If no Qdrant credentials: walk me through cloud.qdrant.io setup
5. If env vars missing: help add to shell profile (QDRANT_CLAUDE_SESSIONS_ENDPOINT, QDRANT_CLAUDE_SESSIONS_API_KEY, JACKED_USER_NAME)
6. If hook/agents not installed: jacked install
7. If no indexed sessions: jacked backfill

VERIFY: jacked status && jacked configure --show

Ask if this is personal use or team setup.
If team: explain that everyone needs the same Qdrant cluster credentials.

WINDOWS NOTES:
- pipx installs jacked to: C:\Users\<user>\pipx\venvs\claude-jacked\Scripts\jacked.exe
- If "jacked" isn't found, find it with: where jacked OR dir C:\Users\%USERNAME%\pipx\venvs\claude-jacked\Scripts\jacked.exe
- In Git Bash, backslash paths get mangled. Use: cmd.exe /c "C:\full\path\to\jacked.exe <command>"

---

What's In Here

Component	Description
jacked CLI	Cross-machine semantic search for Claude Code sessions via Qdrant
10 Agents	Double-check reviewer, PR workflow, test coverage, code simplicity, and more
2 Commands	/dc (double-check), /pr (PR workflow)
1 Skill	/jacked for searching past sessions from within Claude

Why This Exists

Claude Code has a context problem:

1. Sessions don't sync across machines - Work on your desktop, can't resume on laptop
2. Auto-compact destroys context - Hit the limit and your carefully built context gets summarized into oblivion
3. Finding past work is painful - "How did I solve that auth bug last week?" means grep-ing through JSONL files

This repo addresses these problems:

• jacked indexes all your sessions to Qdrant Cloud for semantic search from anywhere
• Agents like double-check-reviewer catch mistakes before they ship
• Commands like /dc trigger comprehensive reviews at the right moments

The goal: never lose useful context, never repeat solved problems, catch issues early.

---

Manual Install

Install the CLI

Use pipx (recommended - installs globally, always on PATH):

pipx install claude-jacked

Don't have pipx? pip install pipx && pipx ensurepath

Why not regular pip? If you pip install into a conda env or virtualenv, the jacked command only works when that env is active. Claude Code hooks run in a fresh shell without your env activated → jacked: command not found. pipx avoids this by installing to an isolated global location that's always on PATH.

Set Up Qdrant Cloud

The session search features require Qdrant Cloud for vector storage and embedding:

1. Sign up at cloud.qdrant.io (requires paid tier ~$30/mo for server-side embedding)
2. Create a cluster and get your URL + API key
3. Add to your shell profile:

export QDRANT_CLAUDE_SESSIONS_ENDPOINT="https://your-cluster.qdrant.io"
export QDRANT_CLAUDE_SESSIONS_API_KEY="your-api-key"

Install Everything

jacked install

This installs:

• All agents to ~/.claude/agents/
• All commands to ~/.claude/commands/
• The /jacked skill to ~/.claude/skills/
• Auto-index hook (indexes sessions after every Claude response)

Restart Claude Code after running this.

Index Your Sessions

jacked backfill        # Index all existing sessions
jacked status          # Verify it's working
jacked search "something you worked on before"

Note: If you only want the agents and commands (not the session search), you can manually copy just those files from the repo without setting up Qdrant. But the main jacked functionality requires it.

---

Team Setup

Share knowledge across your team by using the same Qdrant cluster.

How It Works

1. Everyone on the team uses the same QDRANT_CLAUDE_SESSIONS_ENDPOINT and QDRANT_CLAUDE_SESSIONS_API_KEY
2. Each person sets their JACKED_USER_NAME to identify their sessions
3. Search results show who created each session (YOU vs @teammate)
4. Ranking prioritizes your own sessions, then teammates, with recency boost

Team Environment Setup

# Everyone uses the same cluster
export QDRANT_CLAUDE_SESSIONS_ENDPOINT="https://team-cluster.qdrant.io"
export QDRANT_CLAUDE_SESSIONS_API_KEY="team-api-key"

# Each person sets their name
export JACKED_USER_NAME="sarah"  # or "mike", "jack", etc.

Search Examples

jacked search "auth implementation"     # Ranked: your stuff first, then team
jacked search "auth" --mine             # Only your sessions
jacked search "auth" --user sarah       # Only Sarah's sessions

Multi-Factor Ranking

Results are ranked by:

Factor	Weight	Description
Semantic	Core	How well the query matches the session content
Ownership	1.0 / 0.8	Your sessions weighted higher than teammates
Repository	1.0 / 0.7	Current repo weighted higher than others
Recency	Decay	Recent sessions weighted higher (35-week half-life)

Customize weights via environment variables:

export JACKED_TEAMMATE_WEIGHT=0.8        # Teammate session multiplier
export JACKED_OTHER_REPO_WEIGHT=0.7      # Other repo multiplier
export JACKED_TIME_DECAY_HALFLIFE_WEEKS=35  # Weeks until half relevance

---

Agents

Installed automatically by jacked install to ~/.claude/agents/.

Agent	What It Does
double-check-reviewer	CTO/CSO-level review for security, auth gaps, data leaks
code-simplicity-reviewer	Reviews for over-engineering and unnecessary complexity
defensive-error-handler	Audits error handling and adds defensive patterns
git-pr-workflow-manager	Manages branches, commits, and PR organization
pr-workflow-checker	Checks PR status and handles PR lifecycle
issue-pr-coordinator	Scans issues, groups related ones, manages PR workflows
test-coverage-engineer	Analyzes and improves test coverage
test-coverage-improver	Adds doctests and test files systematically
readme-maintainer	Keeps README in sync with code changes
wiki-documentation-architect	Creates/maintains GitHub Wiki documentation

Usage

Claude automatically uses these agents when appropriate. You can also invoke them explicitly:

Use the double-check-reviewer agent to review what we just built

---

Commands

Installed automatically by jacked install to ~/.claude/commands/.

Command	What It Does
/dc	Triggers comprehensive double-check review (auto-detects if planning vs implementation)
/pr	Checks PR status, manages workflow for current branch

Usage

/dc          # Review current work
/pr          # Check PR status

---

Skills

Installed automatically by jacked install to ~/.claude/skills/.

Skill	What It Does
/jacked	Search past sessions and load context

Usage

/jacked implement user authentication

Claude searches your indexed sessions, shows matches, and lets you load relevant context.

Note: Searches all indexed sessions (yours + teammates if team setup). Results are ranked by: semantic match × ownership (yours first) × repo (current first) × recency. Use --mine for only your sessions.

---

Jacked CLI Reference

Commands

jacked search "query"              # Semantic search with multi-factor ranking
jacked search "query" --mine       # Only your sessions
jacked search "query" --user sarah # Only this teammate's sessions
jacked search "query" --repo path  # Boost results from this repo

jacked list                        # List indexed sessions
jacked list --repo myproject       # Filter by repo name

jacked retrieve <session_id>       # Get full transcript
jacked retrieve <id1> <id2>        # Get multiple transcripts
jacked retrieve <id> --summary     # Get summary only

jacked index /path/to/session.jsonl --repo /path  # Index specific session
jacked backfill                    # Index all existing sessions
jacked backfill --force            # Re-index everything

jacked status                      # Check Qdrant connectivity
jacked delete <session_id>         # Remove session from index
jacked install                     # Install hook + skill + agents + commands
jacked configure                   # Show config help
jacked configure --show            # Show current config values

How It Works

┌─────────────────────────────────────────────────────────────┐
│  YOUR MACHINE                                               │
│                                                             │
│  Claude Code                                                │
│  ├── Stop hook → jacked index (after every response)        │
│  └── /jacked skill → search + load context                  │
│                                                             │
│  ~/.claude/projects/                                        │
│  └── {repo}/                                                │
│      └── {session}.jsonl  ←── parsed and indexed            │
└─────────────────────────────────────────────────────────────┘
                            │
                            │ HTTPS
                            ▼
┌─────────────────────────────────────────────────────────────┐
│  QDRANT CLOUD                                               │
│                                                             │
│  • Server-side embedding (no local ML needed)               │
│  • Vectors + full transcripts stored                        │
│  • Accessible from any machine                              │
└─────────────────────────────────────────────────────────────┘

---

Configuration

Environment Variables

Required:

Variable	Description
QDRANT_CLAUDE_SESSIONS_ENDPOINT	Qdrant Cloud cluster URL
QDRANT_CLAUDE_SESSIONS_API_KEY	Qdrant API key

Identity (for team sharing):

Variable	Default	Description
JACKED_USER_NAME	git user.name	Your name for session attribution
SMART_FORK_MACHINE_NAME	hostname	Override machine name

Ranking weights:

Variable	Default	Description
JACKED_TEAMMATE_WEIGHT	0.8	Multiplier for teammate sessions
JACKED_OTHER_REPO_WEIGHT	0.7	Multiplier for other repos
JACKED_TIME_DECAY_HALFLIFE_WEEKS	35	Weeks until session relevance halves

Other:

Variable	Default	Description
QDRANT_CLAUDE_SESSIONS_COLLECTION	claude_sessions	Collection name
CLAUDE_PROJECTS_DIR	~/.claude/projects	Claude projects directory

Hook Configuration

The jacked install command adds this to ~/.claude/settings.json:

{
  "hooks": {
    "Stop": [{
      "matcher": "",
      "hooks": [{
        "type": "command",
        "command": "jacked index --repo \"$CLAUDE_PROJECT_DIR\""
      }]
    }]
  }
}

---

Security Warning

Jacked sends session data to Qdrant Cloud. This includes:

• Full conversation transcripts
• Repo paths and machine names
• Anything you paste into sessions (including secrets)

Recommendations:

• Don't paste API keys/passwords in Claude sessions
• Keep your Qdrant API key secure
• Consider self-hosting Qdrant for sensitive work

---

Troubleshooting

"QDRANT_CLAUDE_SESSIONS_ENDPOINT not set"

Add to your shell profile (~/.bashrc, ~/.zshrc, or PowerShell profile):

export QDRANT_CLAUDE_SESSIONS_ENDPOINT="https://your-cluster.qdrant.io"
export QDRANT_CLAUDE_SESSIONS_API_KEY="your-key"

"No matching sessions found"

jacked backfill  # Index existing sessions first
jacked status    # Verify connectivity

"jacked: command not found"

You probably installed with pip into a virtualenv/conda env that isn't active. Fix:

pipx install claude-jacked

This installs globally so the hook can find it regardless of which env is active.

Windows: Path Issues in Git Bash

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.

Where pipx installs jacked on Windows:

C:\Users\<your-username>\pipx\venvs\claude-jacked\Scripts\jacked.exe

Solutions:

1. Use cmd.exe wrapper (most reliable in Git Bash):

   cmd.exe /c "C:\Users\jack\pipx\venvs\claude-jacked\Scripts\jacked.exe status"
   

2. Add Scripts folder to PATH (one-time fix): Add C:\Users\<you>\pipx\venvs\claude-jacked\Scripts to your Windows PATH environment variable.

3. Use forward slashes (sometimes works):

   /c/Users/jack/pipx/venvs/claude-jacked/Scripts/jacked.exe status
   

Finding where jacked is installed:

where jacked

or

dir C:\Users\%USERNAME%\pipx\venvs\claude-jacked\Scripts\jacked.exe

Agents not loading

Make sure files are in the right place:

• Global: ~/.claude/agents/
• Project: .claude/agents/ in your repo root

---

Development

git clone https://github.com/jackneil/claude-jacked
cd claude-jacked
pip install -e ".[dev]"
pytest

---

License

MIT

Credits

Built for Claude Code by Anthropic.

Uses Qdrant for vector search.