How this command is triggered — by the user, by Claude, or both
Slash command
/claude-recall:setupThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
You are helping the user set up the claude-recall statusline plugin. Follow these steps: 1. Read `~/.claude/settings.json` to check the current configuration. 2. Find the plugin cache path by searching for `dist/statusline.js` under `~/.claude/plugins/cache/`: - Use Glob: `~/.claude/plugins/cache/**/claude-recall/**/dist/statusline.js` - If multiple versions found, pick the one with the highest version number - Extract the plugin root (everything before `/dist/statusline.js`) - If not found in cache, fall back to the current working directory 3. **Create a launcher script** ...
You are helping the user set up the claude-recall statusline plugin.
Follow these steps:
Read ~/.claude/settings.json to check the current configuration.
Find the plugin cache path by searching for dist/statusline.js under ~/.claude/plugins/cache/:
~/.claude/plugins/cache/**/claude-recall/**/dist/statusline.js/dist/statusline.js)Create a launcher script at ~/.claude/claude-recall/statusline-launcher.sh with this exact content:
#!/bin/bash
DIR=$(find ~/.claude/plugins/cache -path '*/claude-recall/*/dist/statusline.js' -type f 2>/dev/null | sed 's#/dist/statusline.js$##' | sort -V | tail -1)
if [ -n "$DIR" ]; then
exec node "${DIR}/dist/statusline.js"
fi
Make it executable: chmod +x ~/.claude/claude-recall/statusline-launcher.sh
Merge the statusLine configuration into ~/.claude/settings.json:
{
"statusLine": {
"type": "command",
"command": "bash ~/.claude/claude-recall/statusline-launcher.sh",
"padding": 1,
"refreshInterval": 30
}
}
Preserve all existing settings — only add/update the statusLine key.
padding: 1 adds one column of horizontal breathing room around the statusline.refreshInterval: 30 re-runs the statusline every 30 seconds so the Line 2 elapsed clock stays accurate while the main session is idle. Remove the field to disable idle refreshes.Verify that these files exist (relative to plugin root found in step 2):
hooks/hooks.jsondist/statusline.jsdist/hooks/session-start.jsdist/hooks/prompt-submit.jsdist/hooks/cwd-changed.jsdist/hooks/trigger-refinement.jsReport what was configured and tell the user to restart Claude Code for the statusline to take effect. Mention that future plugin updates will be picked up automatically without running /setup again.
npx claudepluginhub dkstm95/claude-recall --plugin claude-recall/setupInitializes or resumes project setup via interactive Q&A, creating conductor/ artifacts for product definition, guidelines, tech stack, workflow, and style guides.
/setupWalks an enterprise admin through configuring the Claude Office add-in to call their own cloud (Vertex, Bedrock, Foundry, or gateway), producing a customized manifest.xml for M365 deployment.
/setupChecks local Codex CLI readiness, prompts to install if unavailable via npm, and optionally toggles stop-time review gate.
/setupInteractive setup wizard that detects installed AI providers, configures authentication, and optimizes token usage. Auto-runs on first install and surfaces a status dashboard on manual invocation.