AI takeover
AI takeover lets AI reply on your behalf. It is controlled at two levels:
- Account-level master switch: when off, no conversation can be taken over by AI.
- Conversation-level takeover: after the master switch is on, choose which AI backend handles a specific conversation.
1. Turn on the master switch
Open Me → Settings → AI assistant and enable the AI takeover master switch.
If the master switch is off, selecting AI in a conversation shows “Enable the AI takeover master switch in Settings first”.
2. Choose an AI backend
Open the conversation menu (⋯) → AI takeover and choose:
| Option | Description | Requirements |
|---|---|---|
| Built-in AI | Uses ClientX’s built-in AI engine | Configure a model key in Settings → AI assistant → Model key configuration |
| External AI model | Calls a model through the local connector (the UI lists available models) | Connector online and local authorization completed |
| Off | Stops AI takeover for this conversation | — |
When using an external AI model you can also:
- Choose a connector (when multiple connectors exist).
- Choose a model (the backend default is used otherwise).
- Set max rounds: the maximum number of automatic replies in a window, preventing infinite loops when both sides enable takeover. The default is 8 rounds over about 5 minutes.
Click Confirm to save.
3. Trigger rules
- Direct messages: AI replies automatically after the other person sends a message.
- Group chats / channels: you must @mention the AI account (nickname or email); without a mention there is no reply.
- AI replies are marked with [AI assistant] so they can be distinguished from human replies.
- Your own messages do not trigger your own AI takeover.
4. Turn it off
Choose Off in the same AI takeover dialog, or turn off the account-level master switch. Re-enabling takeover starts a fresh context.
5. Connectors and authorization
External AI models use the local connector:
- The connector runs on a computer with the relevant CLI installed and signed in.
- On the first takeover or when switching conversations, you may need to open the authorization URL in a browser on the connector machine and click Confirm.
- If you see “Waiting for local confirmation”, “Unreachable” or “Offline”, check that the connector is running, the address is correct and the account has connector execution permission.
6. AI conversations
“Messages → New conversation → AI conversation” creates a standalone AI session. Its backend is chosen inside the conversation and is always enabled, independent of the AI takeover master switch.
7. FAQ
AI is selected but there is no reply? Check: master switch → conversation-level AI selection → @mention in groups → model key/connector readiness → max rounds.
“No API key configured”? Add a key in Settings → AI assistant → Model key configuration, or switch to a ready connector backend.
Too many or looping replies? Lower the max rounds. The limit terminates loops when both sides enable takeover.
Why can the connector only run locally? It reuses the local AI client login state and keys; those credentials cannot leave the machine.
Third-party names
Third-party product names in this page are used only to describe compatibility and operation paths, and belong to their respective owners. No endorsement, sponsorship or affiliation is implied.