Server and connections
Agents run on their registered computer. The messaging service receives callbacks from WhatsApp, Slack and Google Chat and routes conversations to those agents. Native chats do not need that service.
Choose a server
Open Settings → Server and select the location:
| Choice | Requirements | Data and operation |
|---|---|---|
| This computer | Docker and a reachable HTTPS address for messaging callbacks | You operate messaging, credentials and storage here |
| Your own server | Existing service URL and connector token, or supported WhatsApp pairing | Its administrator operates messaging; agents still run here |
| CatalEx Cloud | Sign-in and a service offered by your setup | CatalEx operates the connected messaging service |
Save before starting. Switching a running setup briefly stops and restarts it. Switching server identity sets the earlier connection and its conversations aside; reconnecting to it brings them back. It does not move or delete data on either server. Review the app’s switch confirmation.
For a server token, use the private app field; leaving it blank keeps the saved token. From the terminal:
catalex connections hosting show
catalex connections hosting set --url https://YOUR-SERVICE --token-file /absolute/private/token
Use a token file owned by you with mode 0600. A connector token is not an administrator credential. Remote account administration may need the server administrator.
Public address and tunnel
Slack, Meta and Google need to reach the messaging callback over public HTTPS. Follow the forwarding destination shown by setup. Never expose the agent control endpoint as a callback. Keep a tunnel running while messaging is in use; if its public origin changes, follow each account’s repair steps to update provider configuration.
The setup command supports managed-tunnel flags; read catalex setup --help for installed options. Select your tunnel service explicitly before authorizing provisioning. Credentials and provider approvals remain private person steps.
Disconnect and reconnect
catalex connections hosting off
catalex connections hosting on
These disconnect or reconnect the selected computer’s saved messaging service. on reuses the previous service identity. catalex local-setup off stops the complete setup on this computer and removes its messaging containers while keeping saved data. catalex local-setup on enables it again. Replacing a remote identity requires explicit --replace-identity; inspect the current connection first.
Control another computer
A saved connection tells the app/client how to reach an existing agent computer; it does not install CatalEx there. Use a reachable origin and that computer’s control token, kept in a private file:
catalex connections add office --url https://YOUR-COMPUTER --token-file /absolute/private/control-token
catalex connections list
catalex --connection office status
catalex connections use office
Do not confuse this control token with a messaging connector token. The first administers the agent computer; the second connects it to messaging. Inspect the selected connection before any mutation. Use connections edit, remove and rescan --dashboard as described in their help. Removing a saved reference does not uninstall the remote computer.
CatalEx account and pairing
Use the app’s account menu to sign in or out. Local native chats do not require sign-in. Cloud hosting and CatalEx-managed WhatsApp pairing may require it; follow the address and pairing instructions supplied by the app. Do not create a new account to recover an installation owned by an existing one.
When the Server page offers syncing earlier AI conversations, read its state. Incomplete, waiting or unsupported does not confirm all history is available on the server. See Privacy Policy for the data implications of a service connection.