> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vulpy.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Missions: guided setup and daily shop ops

> Missions turn store setup into a managed process. Follow the first-boot flow in the WebUI, then let Fox handle ongoing catalog, content, and analytics work.

Missions are the guided flows that Fox drives inside the Vulpy WebUI. A first-boot mission takes you from a bootstrapped install to a healthy running shop. From there, ongoing missions cover product and catalog work, content, orders, and analytics, all through the same WebUI.

<Tip>
  **Ask Fox to run the mission.** Missions are Fox-driven flows; you don't run them manually, you tell Fox to start.

  Try prompts like:

  * "Start the first-boot mission."
  * "What onboarding steps are left?"
  * "Kick off the daily catalog check."
</Tip>

## First-boot onboarding

The welcome feature walks you through setting up your store while Fox works alongside you in the same checkout.

<Steps>
  <Step title="Open the Vulpy WebUI">
    Start Fox with `pnpm db:hermes:up` and open [http://localhost:8787](http://localhost:8787).
  </Step>

  <Step title="Complete the welcome flow">
    Fill in the guided steps in the welcome feature. Fox brings up storefront, Medusa, and Postgres, runs migrations, seeds the catalog, and confirms services are healthy.
  </Step>

  <Step title="Verify the shop">
    Open the storefront at [http://localhost:3000](http://localhost:3000) and the Medusa admin at [http://localhost:9000/app](http://localhost:9000/app). Sign in with `admin@example.com` / `supersecret` (or your reset password).
  </Step>
</Steps>

## Ongoing missions

Once your dev shop is up, Fox stays available for day-to-day operational work: creating products, dressing category pages with Payload, resending order confirmations, adding Matomo events on new features. Fox works in the same checkout you do, so any file it touches is immediately reflected on the host.

<Tip>
  You approve every environment action in the WebUI before Fox runs it. Fox never has Docker socket access.
</Tip>

## What Fox will not do

Fox is restricted to dev by design. Staging and live are human-only:

* `pnpm vulpy env add|up|down|golive` refuse inside the Hermes container.
* Live and staging environment directories are hidden from Fox's mount.
* On AWS, the IMDS lock blocks instance metadata by default so Fox cannot use the VM IAM role.

<Warning>
  If a mission ever tells you to run a live or staging command yourself, that is intentional. Fox proposes; you dispatch human-scope operations from the host.
</Warning>

<CardGroup cols={2}>
  <Card title="Environment context and actions" icon="satellite-dish" href="/fox/environment-context">
    How the WebUI shows live state and how you approve actions.
  </Card>

  <Card title="Go live" icon="rocket" href="/deploy/going-live">
    Move from dev-plus-Fox to a real live shop.
  </Card>
</CardGroup>