rhythmic-flower-10210
05/13/2025, 7:23 AMtall-airline-16756
05/13/2025, 7:23 AMtall-airline-16756
05/13/2025, 7:23 AMquery_info
, or Manual Retrieval for fine-grained control by injecting retrieved context into prompts.
• Voice Pipeline Agent: This allows you to modify the LLM response directly, providing greater control over the conversation flow.
The Query Engine is currently the recommended approach as it offers a good balance of flexibility and control. Let me know if you need further details on any of these options!
Sources: AI voice agents | LiveKit Docs | AI voice agents | LiveKit Docs | Tree View: | dse-workbench | Tree View: | dse-workbenchrhythmic-flower-10210
05/13/2025, 7:24 AMtall-airline-16756
05/13/2025, 7:24 AM@llm.ai_callable
decorator has been replaced with the @function_tool
decorator.
• Functions defined with @function_tool
are automatically accessible to the LLM, eliminating the need for a separate llm.FunctionContext
class.
• Argument types are inferred from the function signature and docstring, and annotated types are no longer supported.
• Functions now take a RunContext
object, which provides access to the current agent state.
This new system simplifies the process of defining and maintaining tools for agents. Let me know if you need further clarification!
Sources: Agents 0.x migration guide | LiveKit Docsrhythmic-flower-10210
05/13/2025, 7:25 AMtall-airline-16756
05/13/2025, 7:25 AM@function_tool
decorator is the standard and recommended way to define tools for agents. Currently, there are no direct alternatives to this method in version 1.0, as it has replaced the older @llm.ai_callable
decorator from previous versions.
This approach simplifies tool definition by making them automatically accessible to the LLM without requiring additional setup. If you have specific requirements or challenges with @function_tool
, feel free to share, and I can assist further!
Sources: Function calling with Voice Agents | LiveKit Docs | Agents 0.x migration guide | LiveKit Docs