--- url: https://docs.codefox.ai/self-host/running-culpeo.md --- # Running Culpeo This page covers what is specific to running Culpeo, the support chat, on your server: its first account, its data, its Slack connection, and what a restore changes. ## Where it runs | | | |---|---| | Folder | `/opt/communications` | | Address | `agent.` | | On the server | `127.0.0.1:3024` | | Services | `app`, `worker`, `db`, `migrate`, `updater` | | Settings | [Culpeo settings](/reference/settings/culpeo) | In `foxden` commands, name it `culpeo` or `communications`, for example `foxden status --product culpeo`. ## The first account Culpeo has no setup link of its own: install it with Foxden Admin. When you pick Culpeo alone in the `foxden init` wizard, the installer adds Admin beside it. People then sign in to Culpeo through Admin, and the level each person has in Admin decides what they can do in Culpeo. The first person to sign in to Culpeo through Admin creates its first account. At that moment Culpeo sets each of its inboxes to **Drafts for human review**: a person can ask the AI for a suggested reply or a summary, and a person reads and sends every reply. An inbox added later starts with AI off, and each inbox's AI settings change it. AI runs through Admin's AI gateway, so it needs a provider key there; see [AI](/run-your-company/ai). ## Its data * **Database**: conversations, inboxes and settings. * **Attachments**: files pasted into a conversation, in Culpeo's data folder (`culpeo-data`). On a server with Library, the files Culpeo stores once it is linked to Library are kept in Library instead. The nightly backup at 01:50 holds the database and the data folder. See [Back up and restore](/self-host/backup). ## Slack An inbox can answer in Slack. Its tokens are entered in Culpeo's **Settings** › **Slack**, and stored sealed under Culpeo's `APP_SECRET`. The installer can also take the Slack bot token, signing secret and app-level token; leave them blank to connect Slack in Culpeo's settings later. The app-level token is only for Socket Mode, when Slack cannot reach your server. ## Visitor checks Culpeo can check new chat visitors with Cloudflare Turnstile. Set `COMMUNICATIONS_TURNSTILE_SITE_KEY` and `COMMUNICATIONS_TURNSTILE_SECRET_KEY`, and add Culpeo's address to the widget in Cloudflare (or list the names in `COMMUNICATIONS_TURNSTILE_HOSTNAMES`). While Culpeo's address is missing from the widget, every new visitor is refused. ## Email Culpeo emails a visitor to reopen their conversation. It sends through Resend only, with its own `COMMUNICATIONS_RESEND_API_KEY` and `COMMUNICATIONS_EMAIL_FROM`, which `foxden email set` and **Server** › **Connections** write for you. See [Set up outgoing email](/self-host/email). ## After a restore `foxden backup restore` gives Culpeo a new `APP_SECRET`, on the same server or a new one. Because the Slack and WhatsApp tokens are sealed under it: 1. Paste the Slack bot token, signing secret and app-level token again in **Settings** › **Slack**. Existing threads carry on. 2. On a new address, change the Slack app's Request URLs to it and verify them in Slack. 3. If WhatsApp is connected, paste its access token, app secret and verify token again in **Settings** › **WhatsApp**. On a new address, change the Callback URL in Meta's WhatsApp settings too. 4. On a new address, add it to the Turnstile widget in Cloudflare. Visitor links that reopen a conversation, and staff sessions, stop working; people sign in again.