Skip to content

Conversation

@markbackman
Copy link
Contributor

Please describe the changes in your PR. If it is addressing an issue, please reference that as well.

@codecov
Copy link

codecov bot commented Sep 21, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@golbin
Copy link
Contributor

golbin commented Sep 22, 2025

By the way, it would be great if you could also distribute custom services, processors, and transports via pip as plugins. That way, developers could use Pipecat more flexibly.

@markbackman
Copy link
Contributor Author

markbackman commented Sep 22, 2025

By the way, it would be great if you could also distribute custom services, processors, and transports via pip as plugins. That way, developers could use Pipecat more flexibly.

Just to make sure I understand, you're talking about the third-party integration, right? I've included a Packaging and Distribution section, where I say: - Consider releasing to PyPI for easier installation. pip installation pulls from PyPI, so you would be able to pip install a custom package; that's the idea.

@golbin
Copy link
Contributor

golbin commented Sep 22, 2025

Yes. For example, let’s say I’ve built my own LLM called g-llm or a service like openai-custom-service. I’d like to be able to package them so that others can simply run pip install g-llm or pip install openai-custom-service and then use them as plugins within Pipecat.

@golbin
Copy link
Contributor

golbin commented Sep 22, 2025

Another benefit of this approach is that if a plugin from another service has a bug or adds new features, we don’t need to wait for Pipecat itself to be modified or updated.

Copy link
Contributor

@vr000m vr000m left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@filipi87 filipi87 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have made a couple of minor suggestions, but as it is now, it’s already a great starting point. 🎉

@markbackman markbackman force-pushed the mb/third-party-integrations branch 2 times, most recently from c7dc66d to 1fc2162 Compare September 30, 2025 14:31
@markbackman markbackman marked this pull request as ready for review September 30, 2025 14:32
Copy link
Contributor

@mattieruth mattieruth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shmantastic!

@markbackman markbackman force-pushed the mb/third-party-integrations branch from ec14453 to 8367199 Compare October 2, 2025 19:46
@markbackman markbackman force-pushed the mb/third-party-integrations branch from 8367199 to b669e3a Compare October 2, 2025 19:54
@markbackman markbackman merged commit 62a5f07 into main Oct 2, 2025
6 checks passed
@markbackman markbackman deleted the mb/third-party-integrations branch October 2, 2025 19:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants