Chat Mode
Configure your agent for text-only conversations with chat mode
Configure your agent for text-only conversations with chat mode
Chat mode allows your agents to act as chat agents, ie to have text-only conversations without audio input/output. This is useful for building chat interfaces, testing agents, or when audio is not required.
There are two main ways to enable chat mode:
This guide covers both approaches and how to implement chat mode across different SDKs.
Configure an agent for text-only mode to make it the default for every conversation with that agent.
Open your agent in the dashboard, navigate to the Advanced tab, and enable the Text only toggle. Save your changes.
For complete API reference and all available configuration options, see the text only field in Create Agent API documentation.
To enable chat mode at runtime using overrides (rather than configuring at the agent level), you can use the textOnly override in your conversation configuration:
This configuration ensures that:
Critical: When using chat mode, you must ensure the agent_response event/callback is
activated and properly configured. Without this, the agent’s text responses will not be sent or
displayed to the user.
Security Overrides: When using runtime overrides (not agent-level configuration), you must enable the conversation overrides in your agent’s security settings. Navigate to your agent’s Security tab and enable the appropriate overrides. For more details, see the Overrides documentation.
Agent Response Event: Always configure the agent_response callback or event handler to receive and display the agent’s text messages.
Agent Configuration: If your agent is specifically set to chat mode in the agent settings, it will automatically use text-only conversations without requiring the override.
No Audio Interface: When using text-only mode, you don’t need to configure audio interfaces or request microphone permissions.
In chat mode, you’ll need to send user messages programmatically instead of through audio:
Chat mode provides significant concurrency advantages over voice conversations:
During connection initiation, chat-only conversations are initially checked against your total concurrency limit during the handshake process, then transferred to the separate chat-only concurrency pool once the connection is established.
Chat mode is ideal for:
If the agent’s responses are not appearing:
agent_response callback is properly configuredtextOnly override is set