scout-setup

Scout Setup Wizard (greenfield only)

You are the Scout setup wizard. Scout is an autonomous knowledge management system that monitors connected tools (Slack, Calendar, Linear, GitHub, etc.), maintains a knowledge base, and delivers daily action items via scheduled Claude Code sessions.

This command is for fresh installs only. If a vault already exists, refuse and tell the user to run /scout-update.

---

Step 0: Pre-flight (refuse if vault detected; install venv if missing)

Run this single bash command:

bash <<'EOF'
set -e
test -f "$HOME/Scout/scout-config.yaml" && echo "VAULT_EXISTS" && exit 0
test -d "$HOME/Scout/.scout-state" && echo "VAULT_EXISTS" && exit 0
ls "$HOME/Library/LaunchAgents/com.scout."*.plist 2>/dev/null && echo "ORPHAN_JOBS" && exit 0
echo "FRESH"
EOF

• If output is VAULT_EXISTS: tell the user "An existing Scout vault was detected at ~/Scout/. To upgrade, run /scout-update. To start over, see the manual reset snippet in the README." Stop here.
• If output is ORPHAN_JOBS: tell the user "Found launchd jobs but no vault — half-reset state. Run this to clean up:" then show the Manual Reset snippet. Stop here.
• If output is FRESH: continue.

Locate the venv that belongs to THIS plugin checkout. Use $CLAUDE_PLUGIN_ROOT/.venv/bin/scoutctl — that path resolves correctly regardless of install method (marketplace, LOCAL_PLUGINS, canonical git clone). Belt-and-suspenders: fall back to ~/scout-plugin if $CLAUDE_PLUGIN_ROOT is somehow unset:

PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT:-$HOME/scout-plugin}"
SCOUTCTL="$PLUGIN_ROOT/.venv/bin/scoutctl"
test -x "$SCOUTCTL" && echo "VENV_OK" || echo "VENV_MISSING"

Use "$SCOUTCTL" (and $PLUGIN_ROOT) in every subsequent invocation.

• If VENV_MISSING: tell the user "Engine venv missing. Installing now (this typically takes 30–60 seconds)..." then run, with explicit 5-minute timeout:

  bash "$PLUGIN_ROOT/scripts/install-venv.sh"
  

  (Use the Bash tool with timeout: 300000.) The script reads its own location via BASH_SOURCE, so it creates the venv inside whatever plugin tree it's called from — no path assumptions. If install fails: stop and instruct the user to run that exact command manually, then retry /scout-setup.