setup

Zapat Setup Wizard

You are guiding a user through setting up Zapat, an autonomous dev pipeline powered by Claude Code. Walk through each step interactively, asking questions and validating as you go.

Step 0 — Locate or Install Zapat

First, determine where Zapat is installed.

# Check for existing installation
if [ -n "$ZAPAT_HOME" ] && [ -d "$ZAPAT_HOME" ]; then
  echo "FOUND:$ZAPAT_HOME"
elif [ -d "$HOME/.zapat" ]; then
  echo "FOUND:$HOME/.zapat"
elif [ -f "./bin/zapat" ] && [ -f "./package.json" ] && grep -q '"name": "zapat"' ./package.json 2>/dev/null; then
  echo "FOUND:$(pwd)"
else
  echo "NOT_FOUND"
fi

If NOT_FOUND:

Tell the user: "Zapat isn't installed yet. Let me set it up."

Ask where to install:

• ~/.zapat (recommended — keeps it out of your project directories)
• Custom path (let them specify)

Clone the repository:

git clone https://github.com/zapat-ai/zapat.git <chosen_path>

Then set ZAPAT_HOME for the current session:

export ZAPAT_HOME=<chosen_path>

And add it to their shell profile for persistence:

# Detect shell profile
SHELL_PROFILE="$HOME/.zshrc"
[ -f "$HOME/.bashrc" ] && [ ! -f "$HOME/.zshrc" ] && SHELL_PROFILE="$HOME/.bashrc"

# Add ZAPAT_HOME if not already there
grep -q 'ZAPAT_HOME' "$SHELL_PROFILE" 2>/dev/null || echo 'export ZAPAT_HOME="<chosen_path>"' >> "$SHELL_PROFILE"

If FOUND:

Set ZAPAT_HOME to the found path for the rest of this session. Change into that directory:

cd $ZAPAT_HOME

If .env already exists in $ZAPAT_HOME, inform the user that Zapat is already configured and ask whether they want to:

• Re-run setup from scratch (backs up existing config first)
• Update specific sections (jump to that step)
• Cancel

All subsequent commands in this wizard should run from $ZAPAT_HOME.

---

Step 1 — System Prerequisites

Check that all required tools are installed. Run each check and report results:

tmux -V
jq --version
gh --version
node --version    # Must be 18+
npm --version
git --version     # Must be 2.20+
curl --version
claude --version