setup-oss

OSS Autopilot Setup

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

Input validation: See "AskUserQuestion Validation Protocol" in workflows/reference.md.

Step 0: Ensure CLI is Built and Available

This flow delegates entirely to the CLI. There is no markdown-only fallback — if the CLI cannot be built, ask the user to install Node 22+ and re-run.

Build the CLI on first run (auto-installs deps). Delegates to scripts/build-cli-if-stale.sh (#1292), which detects an existing-but-stale bundle as well as a missing one — the prior existence-only check would happily reuse a bundle from a stale checkout:

CLI_HELPER_RC=0
"${CLAUDE_PLUGIN_ROOT}/scripts/build-cli-if-stale.sh" "${CLAUDE_PLUGIN_ROOT}" >/tmp/oss-setup-cli-build.log 2>&1 || CLI_HELPER_RC=$?
if [ "$CLI_HELPER_RC" = "2" ]; then
  echo "BUILD_FAILED"; tail -5 /tmp/oss-setup-cli-build.log; exit 1
fi

If the build succeeded but the bundle file still isn't there, or if node is unavailable: Stop the flow and tell the user:

"OSS Autopilot setup needs the CLI. Install Node.js 22+ from https://nodejs.org, then re-run /setup-oss. (Alternative: build manually with cd ${CLAUDE_PLUGIN_ROOT}/packages/core && npm install && npm run bundle.)"

If output starts with BUILD_FAILED: Show the error lines and the same install/re-run guidance. Common causes: missing Node 22+, stale node_modules, no network for npm install.

Then verify the CLI is callable:

node "${CLAUDE_PLUGIN_ROOT}/packages/core/dist/cli.bundle.cjs" checkSetup --json 2>/dev/null

If this also fails, surface the install/re-run guidance and stop.

---

Step 1: Check Current Status

Run the setup command to see current configuration:

node "${CLAUDE_PLUGIN_ROOT}/packages/core/dist/cli.bundle.cjs" setup --json 2>/dev/null

If setupComplete: true, ask:

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