DeprecationWarning: get_context_frame() is deprecated - Need clarification on switchLLM compatibility

[obigroup]

Description

I'm encountering a deprecation warning in pipecat-flows when using the manager. The warning indicates that get_context_frame() is deprecated and should be replaced with LLMRunFrame.

Error Message

/...../.venv/lib/python3.13/site-packages/pipecat_flows/manager.py:854: DeprecationWarning: get_context_frame() is deprecated and will be removed in a future version. To trigger an LLM response, use LLMRunFrame instead.
  await self._task.queue_frames([self._context_aggregator.user().get_context_frame()])

Context

According to the pipecat release notes 0.0.82, a new LLMRunFrame was introduced to replace the previous approach:

New approach:

await task.queue_frames([LLMRunFrame()])

Old approach (now deprecated):

await task.queue_frames([context_aggregator.user().get_context_frame()])

Questions

1. Is this deprecation warning expected in pipecat-flows? The warning appears to be coming from the flows manager itself, not user code.

2. Does switchLLM functionality work correctly with pipecat-flows? I'm particularly concerned about compatibility between the new LLMRunFrame approach and the switchLLM feature in flows.

3. Should pipecat-flows be updated to use the new LLMRunFrame? If so, is there a timeline for this update?

Environment

• Python: 3.13
• pipecat-flows: 0.0.20
• pipecat: 0.0.84

Expected Behavior

No deprecation warnings should appear when using pipecat-flows, and switchLLM should work seamlessly with the current pipecat version.

Additional Information

This seems to be an internal issue within pipecat-flows that needs to be addressed to maintain compatibility with the latest pipecat changes.