scout-setup

OSS Scout Setup

Customize your OSS Scout preferences. This is optional — the tool works out of the box with auto-detected settings. Use this command to fine-tune languages, labels, and search preferences.

Step 0: Ensure CLI is Built

if [ ! -f "${CLAUDE_PLUGIN_ROOT}/packages/core/dist/cli.bundle.cjs" ]; then
  if ! BUILD_LOG=$(cd "${CLAUDE_PLUGIN_ROOT}/packages/core" && npm install --ignore-scripts --silent 2>&1 && npm run bundle --silent 2>&1); then
    echo "BUILD_FAILED"; echo "$BUILD_LOG" | tail -5; exit 1
  fi
fi

If output starts with BUILD_FAILED: Tell the user the CLI build failed and show the error lines. Suggest: cd ${CLAUDE_PLUGIN_ROOT}/packages/core && npm install --ignore-scripts && npm run bundle. Common causes: missing Node.js 20+, stale node_modules.

Step 1: Check Prerequisites

Verify GitHub CLI is authenticated:

gh auth status 2>&1

If not authenticated:

"You need the GitHub CLI authenticated. Install from https://cli.github.com/ and run gh auth login."

Then STOP.

Step 2: Check Current Setup

setup is interactive and cannot act as a status probe (it exits with a CONFIGURATION error in non-TTY contexts). Read the preferences instead:

GITHUB_TOKEN=$(gh auth token 2>/dev/null || echo "$GITHUB_TOKEN") node "${CLAUDE_PLUGIN_ROOT}/packages/core/dist/cli.bundle.cjs" config --json 2>/dev/null

Setup is complete when data.githubUsername is non-empty. If it is, ask:

"Setup is already configured. Would you like to reconfigure your settings?"

Options: "Yes, reconfigure" or "No, keep current settings"

If they choose to keep current settings, show current config and exit.

Step 3: Configure Preferences

Drive configuration through config set from this conversation (the interactive setup command requires a real terminal and exits with a CONFIGURATION error when run through the Bash tool). Ask the user for each preference, then apply it. The CLI stores configuration in ~/.oss-scout/state.json.