fix(pipecat-moss): fix compatibility with pipecat-ai 1.1.0 by rohanshrma222 · Pull Request #191 · usemoss/moss

rohanshrma222 · 2026-04-30T08:31:57Z

Pull Request Checklist

Please ensure that your PR meets the following requirements:

I have read the CONTRIBUTING guide.
I have updated the documentation (if applicable).
My code follows the style guidelines of this project.
I have performed a self-review of my own code.
I have added tests that prove my fix is effective or that my feature works.
New and existing unit tests pass locally with my changes.

Description

This PR fixes a complete import failure in pipecat-moss when used with pipecat-ai 1.1.0 (the current latest release).

Pipecat 1.1.0 introduced two breaking API removals that moss_index_processor.py depended on:

LLMMessagesFrame was removed — split into LLMMessagesAppendFrame, LLMMessagesUpdateFrame, and LLMMessagesTransformFrame. Replaced with LLMMessagesUpdateFrame which matches the original behaviour of carrying a full messages list to replace the current context.
OpenAILLMContextFrame and its entire module were deleted — Pipecat unified all provider-specific context frame subclasses into the base LLMContextFrame, with provider formatting handled internally by LLM service adapters. Removed the import and simplified all isinstance checks to use LLMContextFrame directly.

The pyproject.toml version constraint is also tightened from >=0.0.99 to >=1.1.0 to make the supported Pipecat version explicit and prevent silent breakage for users.

Fixes #190

Type of Change

Bug fix (non-breaking change which fixes an issue)
New feature
Breaking change
Documentation update

devin-ai-integration

Devin Review found 3 potential issues.

View 1 additional finding in Devin Review.

devin-ai-integration · 2026-04-30T08:35:31Z

+        if isinstance(frame, LLMContextFrame):
            context = frame.context
-        elif isinstance(frame, LLMMessagesFrame):
+        elif isinstance(frame, LLMMessagesUpdateFrame):
            messages = frame.messages
            context = LLMContext(messages)


🚩 Example apps monkey-patch references removed OpenAILLMContextFrame

The example apps at apps/pipecat-moss/ollama-local/ollama_bot.py:102-116 and apps/pipecat-moss/hume-ollama-local/hume_ollama_bot.py:101-115 monkey-patch MossIndexProcessor.process_frame to check for OpenAILLMContextFrame. With pipecat-ai bumped to >=1.1.0 (where OpenAILLMContextFrame may no longer exist), and the library code no longer handling that frame type, these example apps will likely break at runtime. These apps depend on pipecat-moss>=0.0.1 which would resolve to the new 0.1.0, pulling in pipecat-ai>=1.1.0. The monkey-patches should be updated or removed as part of this migration.

Was this helpful? React with 👍 or 👎 to provide feedback.

devin-ai-integration · 2026-04-30T08:35:33Z

-                await self.push_frame(LLMMessagesFrame(context.get_messages()))
-            elif isinstance(frame, (LLMContextFrame, OpenAILLMContextFrame)):
-                await self.push_frame(type(frame)(context=context))  # type: ignore[arg-type]
+                await self.push_frame(LLMMessagesUpdateFrame(messages=context.get_messages()))


🚩 LLMMessagesUpdateFrame fields beyond 'messages' are not propagated

In moss_index_processor.py:92-94, when an LLMMessagesUpdateFrame is received, only frame.messages is extracted. At line 130, a brand-new LLMMessagesUpdateFrame(messages=context.get_messages()) is pushed, potentially dropping any other fields the original frame carried. The old code did the same with LLMMessagesFrame, so this is pre-existing behavior, not a regression. However, if LLMMessagesUpdateFrame in pipecat 1.1.0 has additional fields (like run_llm seen on LLMMessagesAppendFrame in the example), those would be silently lost. Worth verifying against the pipecat 1.1.0 frame definitions.

Was this helpful? React with 👍 or 👎 to provide feedback.

rohanshrma222 · 2026-04-30T21:28:24Z

@yatharthk2

Please review this PR so that we can move quickly and merge this PR.

yatharthk2

can you please update the changelog. Can be a very generic update message

yatharthk2 · 2026-04-30T22:50:02Z

 [project]
 name = "pipecat-moss"
-version = "0.0.3"
+version = "0.1.0"


can you please make it 0.0.4

yatharthk2 · 2026-04-30T23:08:21Z

can you please provide quick loom video that runs the pipecat-moss/examples

rohanshrma222 · 2026-05-01T04:51:51Z

Fix Summary Table

File Area	Original (broken)	Fixed (now)	Why
Import	LLMRunFrame	LLMMessagesAppendFrame	LLMRunFrame removed in 1.1.0
Import	RTVIConfig present	removed	deleted in 1.1.0
Import	DailyParams present	removed	no Windows wheels
Import	SileroVADAnalyzer present	removed	needs PyTorch
RTVIProcessor()	config=RTVIConfig(config=[...])	no args	RTVIConfig gone
RTVIObserver	no params arg	params=RTVIObserverParams()	required in 1.1.0
System prompt	no greeting instruction	greeting instruction added	LLM needs to know to greet first
on_client_connected	messages.append + LLMRunFrame()	LLMMessagesAppendFrame(run_llm=True)	only user messages satisfy Gemini
Transport params	daily + webrtc options	webrtc only	daily-python no Windows wheels

2026-05-01.10-08-38.mp4

rohanshrma222 · 2026-05-01T05:16:24Z

I made changes in the example demo also, it was following the older version

devin-ai-integration

Devin Review found 3 new potential issues.

View 5 additional findings in Devin Review.

devin-ai-integration · 2026-05-01T05:18:20Z

🚩 Error path in process_frame swallows the original frame

In moss_index_processor.py:136-138, if an exception occurs during retrieval processing, the original frame (LLMContextFrame or LLMMessagesUpdateFrame) is consumed but never forwarded — only an ErrorFrame is pushed. This means the LLM will never receive the user's message, and the conversation will appear to hang. A more robust approach would be to fall back to pushing the original unaugmented frame so the LLM can still respond (just without retrieval context). This is a pre-existing issue not introduced by this PR, but worth noting since the surrounding code was touched.

(Refers to lines 136-138)

Was this helpful? React with 👍 or 👎 to provide feedback.

devin-ai-integration · 2026-05-01T05:18:21Z

    Frame,
    LLMContextFrame,
-    LLMMessagesFrame,
+    LLMMessagesUpdateFrame,


🚩 Semantic difference between LLMMessagesUpdateFrame and old LLMMessagesFrame is unverified

The PR replaces LLMMessagesFrame with LLMMessagesUpdateFrame (moss_index_processor.py:20,92,130). If LLMMessagesUpdateFrame carries different semantics (e.g., a delta/update vs full message list), the logic of creating a new LLMContext from frame.messages and then pushing a new LLMMessagesUpdateFrame(messages=context.get_messages()) could be incorrect. The CHANGELOG describes this as a direct replacement of a removed class, and the uv.lock confirms pipecat-ai 1.1.0 is resolved, so this is likely safe — but it would be worth verifying against the pipecat 1.1.0 release notes or source.

Was this helpful? React with 👍 or 👎 to provide feedback.

Yes, i have verified it by running a internal test for it.

yatharthk2 · 2026-05-06T00:41:01Z

can you please address the devin comments ?

CLAassistant · 2026-05-07T08:07:07Z

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ rohanshrma222
❌ Your Name

Your Name seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

fix(pipecat-moss): fix compatibility with pipecat-ai 1.1.0

515e9cf

rohanshrma222 requested review from CoderOMaster, HarshaNalluru, r4ghu and yatharthk2 as code owners April 30, 2026 08:31

devin-ai-integration Bot reviewed Apr 30, 2026

View reviewed changes

yatharthk2 reviewed Apr 30, 2026

View reviewed changes

update examples for Pipecat 1.1.0 compatibility

f5787d5

This comment was marked as resolved.

Sign in to view

fix pyproject platform config and example greeting

738a926

This comment was marked as resolved.

Sign in to view

restore SileroVADAnalyzer

c66f043

devin-ai-integration Bot reviewed May 1, 2026

View reviewed changes

updated ruff target-version to py311

c1ee3cc

forward original frame on retrieval failure

09bb866

Merge branch 'main' into updatepipecat-moss

00613a1

Conversation

rohanshrma222 commented Apr 30, 2026 • edited by devin-ai-integration Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Pull Request Checklist

Description

Fixes #190

Uh oh!

devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

devin-ai-integration Bot Apr 30, 2026

Choose a reason for hiding this comment

Uh oh!

devin-ai-integration Bot Apr 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

rohanshrma222 commented Apr 30, 2026

Uh oh!

yatharthk2 left a comment

Choose a reason for hiding this comment

Uh oh!

yatharthk2 Apr 30, 2026

Choose a reason for hiding this comment

Uh oh!

yatharthk2 commented Apr 30, 2026

Uh oh!

rohanshrma222 commented May 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Fix Summary Table

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

rohanshrma222 commented May 1, 2026

Uh oh!

devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

devin-ai-integration Bot May 1, 2026

Choose a reason for hiding this comment

Uh oh!

devin-ai-integration Bot May 1, 2026

Choose a reason for hiding this comment

Uh oh!

rohanshrma222 May 6, 2026

Choose a reason for hiding this comment

Uh oh!

yatharthk2 commented May 6, 2026

Uh oh!

CLAassistant commented May 7, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

rohanshrma222 commented Apr 30, 2026 •

edited by devin-ai-integration Bot

Loading

devin-ai-integration Bot Apr 30, 2026 •

edited

Loading

rohanshrma222 commented May 1, 2026 •

edited

Loading