Document NodeConfig.respond_immediately
#236
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
880323c to
dab6da8
Compare
markbackman
reviewed
May 15, 2025
guides/features/pipecat-flows.mdx
Outdated
| ) | ||
| ``` | ||
|
|
||
| Keep in mind that if you specify `respond_immediately=False`, the user may not be aware of the conversational task at hand when entering the node (the bot hasn't told them yet). While it's always important to have guardrails in your node messages to keep the conversation on topic, letting the user speak first makes it even more so. |
markbackman
reviewed
May 15, 2025
| @@ -442,6 +446,25 @@ This ordering ensures proper completion of all operations. | |||
|
|
|||
| Flows comes equipped with pre-canned actions and you can also define your own action behavior. See the [reference docs](/server/frameworks/flows/pipecat-flows#actions) for more information. | |||
|
|
|||
| ## Deciding Who Speaks First | |||
|
|
|||
| 8000 For each node in the conversation, you can decide whether the LLM should respond immediately upon entering the node (the default behavior) or whether the LLM should wait for the user to speak first before responding. You do this using the `respond_immediately` field. | |||
There was a problem hiding this comment.
After this paragraph, perhaps add a <Tip>, saying:
respond_immediatelycan be used in the initial node if you want the user to speak first. You can point to this being common for cases where the agent is making outbound calls, for example.
markbackman
approved these changes
May 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Documents what's implemented in pipecat-ai/pipecat-flows#133