You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/docs/Develop/concepts-voice-mode.mdx
+16-14Lines changed: 16 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,15 @@ slug: /concepts-voice-mode
5
5
6
6
importIconfrom"@site/src/components/icon";
7
7
8
+
:::warning
9
+
Voice mode is deprecated as of Langflow 1.10.
10
+
11
+
The <Iconname="Mic"aria-hidden="true"/> **Microphone** button in the **Playground** now only enables speech-to-text, with no additional voice mode functionality.
12
+
Speech-to-text transcribes speech into the Playground's chat input field, but does not provide voice interaction with the Langflow UI or text-to-speech responses.
13
+
14
+
The `api/v1/voice` WebSocket endpoints described below are still available.
15
+
:::
16
+
8
17
:::info
9
18
Voice mode is not available in Langflow Desktop.
10
19
To use voice mode, [Install the Langflow OSS Python package](/get-started-installation#install-and-run-the-langflow-oss-python-package).
@@ -63,35 +72,28 @@ This option changes both the expected input language and the response language.
63
72
64
73
## Develop applications with websockets endpoints
65
74
66
-
Langflow exposes two OpenAI Realtime API-compatible websocket endpoints for your flows.
67
-
You can build applications against these endpoints the same way you would build against [OpenAI Realtime API websockets](https://platform.openai.com/docs/guides/realtime#connect-with-websockets).
75
+
Langflow exposes an OpenAI Realtime API-compatible websocket endpoint for your flows.
76
+
You can build applications against this endpoint the same way you would build against [OpenAI Realtime API websockets](https://platform.openai.com/docs/guides/realtime#connect-with-websockets).
68
77
69
-
The Langflow API's websockets endpoints require an [OpenAI API key](https://platform.openai.com/docs/overview) for authentication, and they support an optional [ElevenLabs](https://elevenlabs.io) integration with an ElevenLabs API key.
78
+
The Langflow API's websocket endpoint requires an [OpenAI API key](https://platform.openai.com/docs/overview) for authentication, and supports an optional [ElevenLabs](https://elevenlabs.io) integration with an ElevenLabs API key.
70
79
71
-
Additionally, both endpoints require that you provide the flow ID in the endpoint path.
72
-
73
-
### Voice-to-voice audio streaming
74
-
75
-
The `/ws/flow_as_tool/$FLOW_ID` endpoint establishes a connection to OpenAI Realtime voice, and then invokes the specified flow as a tool according to the [OpenAI Realtime model](https://platform.openai.com/docs/guides/realtime-conversations#handling-audio-with-websockets).
76
-
77
-
This approach is ideal for low latency applications, but it is less deterministic because the OpenAI voice-to-voice model determines when to call your flow.
80
+
Additionally, the endpoint requires that you provide the flow ID in the endpoint path.
78
81
79
82
### Speech-to-text audio transcription
80
83
81
84
The `/ws/flow_tts/$FLOW_ID` endpoint converts audio to text using [OpenAI Realtime voice transcription](https://platform.openai.com/docs/guides/realtime-transcription), and then directly invokes the specified flow for each transcript.
82
85
83
-
This approach is more deterministic but has higher latency.
84
-
85
86
This is the mode used in the Langflow **Playground**.
86
87
87
88
### Session IDs for websockets endpoints
88
89
89
-
Both endpoints accept an optional `/$SESSION_ID` path parameter to provide a unique ID for the conversation.
90
+
The endpoint accepts an optional `/$SESSION_ID` path parameter to provide a unique ID for the conversation.
90
91
If omitted, Langflow uses the flow ID as the [session ID](/session-id).
91
92
92
93
However, be aware that voice mode only maintains context within the current conversation instance.
93
94
When you close the **Playground** or end a chat, verbal chat history is discarded and not available for future chat sessions.
94
95
95
96
## See also
96
97
97
-
*[Test flows in the Playground](/concepts-playground)
98
+
*[Test flows in the Playground](/concepts-playground)
Copy file name to clipboardExpand all lines: docs/docs/Develop/contributing-telemetry.mdx
+23-1Lines changed: 23 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,4 +90,26 @@ This telemetry event is sent when an unhandled exception is captured by Langflow
90
90
-**Type**: The exception class name, such as `ValueError`.
91
91
-**Message**: The exception message that was raised.
92
92
-**Context**: Additional contextual information related to where the exception occurred, such as route, component, or operation details, when available.
93
-
-**StackTraceHash**: A hash of the stack trace used to group similar exceptions for easier analysis.
93
+
-**StackTraceHash**: A hash of the stack trace used to group similar exceptions for easier analysis.
94
+
95
+
### Deployment provider
96
+
97
+
This telemetry event is sent for various lifecycle operations on deployment provider accounts, such as create, delete, and update.
98
+
99
+
-**DeploymentAction**: The specific action performed, such as `provider.create` or `provider.delete`.
100
+
-**DeploymentProvider**: The deployment provider used, such as `watsonx-orchestrate`.
101
+
-**DeploymentSeconds**: Duration in seconds for the operation, providing performance insights.
102
+
-**DeploymentSuccess**: Boolean value indicating whether the operation was successful.
103
+
-**DeploymentErrorMessage**: Error message details if the operation was unsuccessful.
104
+
-**WxoTenantId**: A unique identifier for the tenant, populated only for `watsonx-orchestrate` deployments, used to understand multi-tenant usage patterns without collecting personal information.
105
+
106
+
### Deployment
107
+
108
+
This telemetry event is sent for various lifecycle operations on deployment resources, such as create, delete, and update.
109
+
110
+
-**DeploymentAction**: The specific action performed, such as `deployment.create`.
111
+
-**DeploymentProvider**: The deployment provider used, such as `watsonx-orchestrate`.
112
+
-**DeploymentSeconds**: Duration in seconds for the operation, providing performance insights.
113
+
-**DeploymentSuccess**: Boolean value indicating whether the operation was successful.
114
+
-**DeploymentErrorMessage**: Error message details if the operation was unsuccessful.
115
+
-**WxoTenantId**: A unique identifier for the tenant, populated only for `watsonx-orchestrate` deployments, used to understand multi-tenant usage patterns without collecting personal information.
0 commit comments