setup

Molly setup

Interactive setup that takes a user from nothing to a running Molly deployment. It is idempotent: every step checks current state first, so it's safe to re-run and safe to start from a repo that's already cloned. Work through the steps in order and confirm each verification passes before moving on.

Ground rules:

• Never ask the user to paste secrets into chat, and never print secret values (no echo $MOLLY_..., no logging curl requests with resolved tokens). The user puts secrets into .env themselves; you only reference them as $VARS.
• All verification calls below are read-only. The only writes are labeled: creating the tracker database (step 4), the optional Slack test message (step 5), and deployment wiring (step 6). Ask before each write.

1. Get the repo

Check whether you're already inside a clone — the repo root contains AGENTS.md and .warp/skills/molly-sourcing/SKILL.md:

git rev-parse --show-toplevel 2>/dev/null

• If the git root has both marker files, cd to that root and skip cloning.
• If a ./molly-agent directory already exists with those markers, cd molly-agent instead of recloning.
• Otherwise clone and enter it:

git clone https://github.com/warpdotdev/molly-agent.git
cd molly-agent

All later steps run from the repo root.

2. Collect configuration in .env

Create the local config from the template if it doesn't exist (.env is gitignored and never committed):

test -f .env || cp .env.example .env

Then ask the user to open .env in their editor and fill it in themselves — walk them through obtaining each value, one service at a time:

1. Notion — create an internal integration at https://www.notion.so/my-integrations and copy its token → MOLLY_NOTION_API_KEY. Create (or pick) a parent page for Molly's Profile Spec pages, share it with the integration (page → ⋯ → Connections), and copy the 32-hex ID from the page URL → MOLLY_NOTION_PARENT_PAGE_ID.
2. Slack — create a Slack app with a bot token (scopes: chat:write, app_mentions:read) → MOLLY_SLACK_BOT_TOKEN. Pick a sourcing channel, invite the bot, copy the channel ID (channel details → About) → SOURCING_SLACK_CHANNEL_ID.
3. Exa — create an API key at https://exa.ai → MOLLY_EXA_API_KEY.
4. GEM — create an API key in GEM's admin settings → MOLLY_GEM_API_KEY.
5. Tracker — leave MOLLY_TRACKER_DB_ID as the placeholder if the user wants step 4 to create the database for them; otherwise paste an existing database ID.