# First run

Source: <https://devshiftteam.github.io/my-whatsapp-mcp/first-run.html>


After launching an existing [desktop executable](https://devshiftteam.github.io/my-whatsapp-mcp/install/desktop.html), use the private browser owner session that the app opens. For the [Docker preview](https://devshiftteam.github.io/my-whatsapp-mcp/install/docker-compose.html), keep the service running and request your private link:

```sh
docker compose exec wa-indexer wa-indexer owner-link --data-dir /var/lib/wa-indexer/data
```

Open it on the Docker host within **30 seconds**. Repeat the command if it expires or after restart.
Keep the owner link and any pairing QR code private.

## Log in as the archive owner

The local app creates its owner login link; this is separate from WhatsApp pairing and provider login. Keep the app running and open the current link on the archive computer. A stale browser tab after shutdown may need a fresh link. Do not publish the owner port or send the link to an AI client.

## Choose chats and dates before pairing

1. Open **Set up your archive** (later, **Chats and dates**). Choose **Last 30 days**, **Last 90 days**, **A date I choose**, or **All available history**. The start date is inclusive.
2. Select **All chats** or **Only chats I select**, then **Save choices**. On first run the button reads **Link WhatsApp to discover chats**. Selective mode with no selected chats saves no message bodies. Discovery can retain chat metadata before selection.
3. Use **Link WhatsApp** in the WhatsApp connection card, then choose **Show linking code**.
4. On your phone open **WhatsApp → Linked devices → Link a device**, then scan the QR code. Use an account you own or have permission to archive. Request a new code if it expires.
5. Watch **WhatsApp connection**, **Saved messages**, and **Keyword search** in the status panel. After allowed messages arrive, [search](https://devshiftteam.github.io/my-whatsapp-mcp/everyday/search.html) for a known received phrase and open its context.

### Optional Hebrew voice notes

In the local first-run window, choose **Voice notes → Hebrew transcription** to open the [transcription guide](https://devshiftteam.github.io/my-whatsapp-mcp/transcription.html#use-the-browser-setup-guide). It supplies copyable installation, service and archive-launch steps, plus **Check running app** to verify the attached Hebrew worker. You still run the commands in terminals on the archive computer; the browser installs nothing and restarts nothing. Keep your existing data directory and launch settings. You can continue without voice setup and return through **Models and media** later. Remote administration, demo and historical snapshots do not offer this native setup guide.

## Check observed coverage

Wait for messages to arrive after connecting. Check the received count and visible date range, then confirm an actual search result. **All available history** means what WhatsApp supplies to this linked device. Earlier history may still be missing.

Bodies discarded before selecting a chat may be unavailable later. Backfill and retry behavior remains under development; expanding a filter cannot guarantee recovery. A zero count means no import has been observed, even if the connection says connected.

## Understand changes that delete data

Narrowing saved chats or moving the import date later removes stored messages outside that policy. Optional ongoing retention is separate: `0` keeps imported messages; a positive value keeps only that many days. Take a [backup](https://devshiftteam.github.io/my-whatsapp-mcp/maintenance/backups.html) before deliberate policy deletion. Search filters only narrow a view and do not change retention.

[Pause import and disconnect](https://devshiftteam.github.io/my-whatsapp-mcp/user-guide.html#pause-disconnect-or-delete) keep saved messages. Use [troubleshooting](https://devshiftteam.github.io/my-whatsapp-mcp/troubleshooting.html) for missing coverage or reconciliation warnings.