pickup — Claude Code command: what it does, how to install
pickup pulls previous target recon from the Claude-BugHunter ledger to inspect tested endpoints, tech stack, and confirmed findings.
MIT ★ 16,193 updated 2026-10-29
/plugin marketplace add elementalsouls/Claude-BugHunter
/plugin install claude-bughunter@elementalsoulsWhat pickup does
The command loads target records directly from ~/.claude/bughunter/memory/targets/<host>.json. It prints session history, last-seen timestamps, detected technologies, confirmed vulnerabilities, and already probed paths. Author Sachin Sharma renamed it from /resume because Claude Code reserves that keyword for internal session control.
Under the hood, it executes an inline python3 command calling memory.rollup() inside the engine directory. If you run it on a domain before executing /recon and /autopilot, the ledger file will be missing and the command prints a notice instead of data.
What it helps with
- inspect which endpoints were already tested on a target
- review confirmed findings before resuming a bug hunt
- check stored tech stack and session timestamps for a domain
Example prompts for the agent
- /pickup target.com
- /pickup api.target.com
How to install pickup
1Plugin marketplace
/plugin marketplace add elementalsouls/Claude-BugHunter/plugin install claude-bughunter@elementalsouls2Manually: put the files in place
.claude/commands/pickup.mdCall it with /pickup. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/pickup.mdCall it with /prompts:pickup. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/pickup.prompt.mdManually: put the files in place
.gemini/commands/pickup.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about pickup
How to install pickup in Claude Code?
Run /plugin marketplace add elementalsouls/Claude-BugHunter first, then run /plugin install claude-bughunter@elementalsouls.
What does the pickup command do?
It reads the target's rollup JSON file and prints previous hunt sessions, confirmed findings, and untested attack surface.
Why is this command called pickup instead of resume?
The /resume name is a reserved internal command in Claude Code, requiring the author to rename this feature to /pickup.
Source text
pickup.md · MIT
---
name: pickup
description: Pick up a previous hunt on a target — shows hunt history and untested surface from the autopilot ledger. Usage: /pickup target.com
---
# /pickup
Pick up where you left off on a target.
> **Renamed from `/resume`** — `/resume` is a reserved Claude Code command.
## What This Does
1. Reads the target rollup from `~/.claude/bughunter/memory/targets/<host>.json`.
2. Shows hunt history (sessions, last seen, tech stack).
3. Lists confirmed findings and the endpoints already tested.
## Usage
```
/pickup target.com
```
## Implementation
The agent reads the rollup directly:
```bash
python3 -c "import sys; sys.path.insert(0,'engine'); import memory, json; print(json.dumps(memory.rollup('target.com'), indent=2))"
```
## If No Previous Hunt
```
No ledger data for target.com. Run /recon then /autopilot target.com first.
```
© Sachin Sharma · MIT · elementalsouls/Claude-BugHunter