@maximem/waitpro-claude

Turn Claude Code's thinking time into a quick, useful read.

WaitPro fills the dead time while Claude Code is working with a short, relevant read pulled from your own bookmarks. There is no window to draw a card in a terminal, so WaitPro lives in the status line at the bottom of the screen: when you send a prompt and Claude starts working, a compact card appears; when the turn ends, the snippet is marked read and the line goes quiet.

This installer wires the status line and its supporting hooks into Claude Code and stores your Maximem API key securely on your machine.

Contents

• Features
• Requirements
• Quick start
• Commands
• How it works
• Where things are installed
• Security
• Configuration
• Troubleshooting
• Uninstall

Features

• Zero-config install. One command wires everything up and asks only for your API key.
• Non-intrusive. Renders in the status line; it is silent whenever there is nothing to show.
• Never blocks you. Snippets are fetched in the background and never delay your prompt.
• Safe by design. Backs up and merges your Claude Code settings without touching unrelated hooks, and stores your key in a locked-down file, never in logs or in anything Claude can see.
• Multi-session aware. State is keyed by Claude Code session, so parallel terminals never collide.
• Clean uninstall. Removes only what it installed and restores any status line it replaced.

Requirements

• macOS or Linux
• Claude Code
• Node.js >= 16
• bash, jq, and curl available on your PATH
• A Maximem API key (create one at app.maximem.ai)

Quick start

npx @maximem/waitpro-claude init

You will be prompted for your Maximem API key. After it finishes, restart Claude Code so the hooks load. On your next prompt, the WaitPro card appears in the status line.

Non-interactive (CI or scripted installs):

npx @maximem/waitpro-claude init --api-key mx_your_key_here --yes

Re-running init is safe and idempotent; it updates the install in place without duplicating anything.

Commands

| Command | Description | | --- | --- | | waitpro-claude init | Install the scripts, wire the hooks and status line into ~/.claude/settings.json, and store your API key. Safe to re-run. | | waitpro-claude status | Show what is installed and wired up. Never prints your key. | | waitpro-claude uninstall | Remove only WaitPro-owned files and settings, and restore any status line it replaced. |

Options: --api-key mx_..., --force (install even if Claude Code is not detected), --yes (never prompt).

How it works

WaitPro uses Claude Code's hooks and status line:

| Hook | What WaitPro does | | --- | --- | | UserPromptSubmit | Fetches one snippet from the WaitPro API in the background and saves it to a per-session state file. Never blocks your prompt. | | statusLine | Redraws the card from that state on each tick. Silent when there is nothing to show. | | Stop / StopFailure | Marks the shown snippet as read and releases its server-side reservation. | | SessionStart / SessionEnd | Resets and cleans up per-session state. |

Every file and reservation is keyed by the Claude Code session_id, so running several terminals at once stays isolated.

Where things are installed

Everything lives under your Claude Code config directory. No developer or machine-specific paths are hardcoded.

~/.claude/waitpro/
├── scripts/        hooks and status-line renderer
├── sessions/       per-session state, keyed by session_id
├── config/         install metadata
└── credentials     your Maximem API key (chmod 600)

Security

• Your API key is stored in ~/.claude/waitpro/credentials with 600 permissions, kept separate from settings.json, and is never printed, logged, or exposed to Claude.
• init backs up settings.json before editing and merges into it. It never overwrites unrelated hooks, your status line, or any other setting, and never duplicates WaitPro entries when re-run.
• uninstall touches only WaitPro-owned entries and files.

Configuration

WaitPro works out of the box with no configuration. One optional environment variable is available for tuning:

• WAITPRO_MAX_WAIT_S — how long, in seconds, the card stays on screen for a single turn before going silent (default 180).

Troubleshooting

• The card does not appear. Make sure you restarted Claude Code after init, then run waitpro-claude status to confirm the hooks and status line are wired and your key is present.
• command not found for jq or curl. Install them with your package manager (for example brew install jq on macOS).
• Check your setup at any time. waitpro-claude status prints a full report without ever revealing your key.

Uninstall

npx @maximem/waitpro-claude uninstall

This removes the WaitPro scripts, hooks, status line, and stored credential, and restores any status line WaitPro had replaced.

Made by Maximem