Settings
Choose settings at the narrowest useful scope. A global default is for future agents; an agent choice affects that agent; a chat choice affects one conversation.
| Where | What you can change | Why change it? |
|---|---|---|
| Settings → AI tools | Discover, connect and disconnect Codex or Claude Code | Add an installed provider or repair discovery after an update |
| Agent → Configure agent | Name, AI tool, model, effort, isolation, per-person tool routing | Choose how and where the agent works |
| Agent configuration | Engagement frequency, tone, Humanizer | Control useful updates and writing style |
| Agent tools and permissions, when supported | MCP selection, terminal access, approval mode | Limit the native tools available to this agent |
| Agent channels → Edit channel | Account assignment and engagement-frequency override | Route an account and tune conversation cadence |
| Native chat → Chat settings | Model and effort | Use a different model for a particular task |
| Settings → Server | This computer, your server or CatalEx Cloud; connection and pairing | Decide who runs messaging and where its data passes |
| Settings → Channels → account | Connection, credentials, output, approval rules, access and limits | Choose who can reach a bot/number and control its workload |
| Settings → Admin | Administrator accounts and admitted people | Manage agents from an authorized messaging account |
| Account menu | CatalEx sign-in and sign-out | Use account-dependent Cloud and pairing features |
| Command line | New-agent defaults, advanced limits, endpoints and saved connections | Tune capacity or manage another computer |
The app shows only controls supported by the selected computer and service. An unavailable control is not a reason to edit state files directly. Update first or use the installed command’s --help to check support.
Scope and application
Models and AI tools explains defaults and per-chat choices. Engagement and writing explains saved versus applied preferences. Tools and permissions covers native evidence: a saved choice alone does not prove a running session uses it.
Access and limits applies to messaging accounts and agents; advanced settings governs computer-wide capacity and media storage. A rejected settings change names the problem; inspect the current state before retrying a concurrent or uncertain change.
Example: a quiet customer-support agent
Set the agent’s frequency to Low and tone to Professional. Keep approval mode inherited from its native configuration. Allow only the customer service tools it needs. Restrict its test WhatsApp account to your own number, set a per-person hourly limit, then verify a real reply before admitting customers. Frequency controls writing; access lists, tool permissions and rate limits enforce separate boundaries.