Stash prompts for later and pop them back into the input box. A Claude Code mod: instant, no model call, works while Claude is busy, and the stashed text never reaches the model.
A message you type while Claude is working is queued. Claude reads it during the current turn or right after it, so it becomes part of the work in progress. That's right for "also update the docs", and Claude often does those things anyway.
Stash is for prompts you don't want sent yet:
- Side questions. "How does the retry logic decide when to give up?" would derail the task Claude is on. Stash it and ask once the task is done.
- Several ideas at once. Jot down every question or follow-up as it comes to you, then expand on them and send them one at a time, in the order you choose.
In Claude Code:
/plugin install pstash --marketplace maxsoldev/pstash
| Command | Does |
|---|---|
/stash <text> |
Saves the text |
/stash pop |
Pastes the newest stash into the input box (or /stash p) |
/stash yank |
Same as pop, but keeps it in the stash (or /stash y) |
/stash |
Opens the picker |
1. Stash a prompt. Type /stash and the prompt you want to send later.
2. It's saved. Press Enter: the prompt is stashed and the footer count goes up. The stashed text stays out of the chat and out of the model's context.
3. Pop it back. /stash pop pastes the newest stash into the input box, ready to edit or send.
Or pick one. Bare /stash lists everything: 1-9 or ↑↓ highlight a prompt. Then p or Enter pastes it, y pastes it and keeps it, x deletes it. Esc closes. The bottom right shows the version that runs, with · local for a --plugin-dir copy.
One JSON file per project, shared by all sessions: ~/.pstash/<project path with non-alphanumerics as ->.json. Set PSTASH_DIR to move it.
{
"version": 1,
"project": "/Users/max/app",
"items": [
{
"id": "lx2k9a3f",
"text": "how does the retry logic decide when to give up...",
"at": "2026-10-11T14:20:00.000Z",
"from": "claude"
}
]
}Items are newest first, capped at 100, without duplicates. Each change re-reads the file, so sessions don't overwrite each other, and a file that doesn't parse is never overwritten. Any tool that follows this format can share the stash.
What it sends, and where. Nothing. Stashes stay on your machine in ~/.pstash/. The mod makes no network calls and no model calls.
Which programs it runs. None.
What it changes in your prompts. Nothing. It submits no prompts and adds nothing to yours.
What it changes in the chat. In the record of a /stash run it blanks the command's arguments, so the stashed text never reaches Claude. Claude only sees /stash and the short output line, like stashed · 3.
What it reads. The HOME and PSTASH_DIR environment variables, to find the stash folder, and the session's project root, to pick the file. Its own plugin.json, for the version in the picker.
What each hook does.
session.start: adds the/stashcommand, loads the stash count and reads the version.command.runforstash: saves, pops, yanks or opens the picker.session.appendfor command rows: blanks the arguments of a/stashrun.prompt.submit,turn.start,turn.complete: notice a/stashrun outside a turn, so its spinner can be hidden. Prompts pass through unchanged.ui.renderforSpinner: draws the spinner blank while/stashruns outside a turn.ui.renderforSessionMode: addsstash nto the footer.ui.renderfor its pane: draws the picker.ui.focusfor its pane: keeps the highlight on the prompts, sop,yandxalways know which one to act on.
With Task:
task check # tsc, tests, validate --strict
task dev # Claude Code with this checkout instead of the installed pstash
task prod # update the installed pstash from GitHub, then start Claude Code
task shots # re-shoot the screenshots in docs/
task dev uses claude --plugin-dir ., which replaces the installed pstash for that session only. Plain claude still uses the installed copy.



