docs: present Pipecat Flows as built into core Pipecat - #964
Merged
Conversation
Pipecat Flows moved from its standalone package/repo into core Pipecat (pipecat-ai/pipecat#4882). Update the docs so Flows reads as built in rather than a separate add-on: - Drop the separate `uv add pipecat-ai-flows` install; Flows ships with pipecat-ai - Update imports from `pipecat_flows` to `pipecat.flows` - Repoint repo and example links to pipecat-ai/pipecat (examples/flows/) - Point the Flows API reference card at reference-server.pipecat.ai - Reword "add-on framework" and the Pipecat/Flows relationship section to describe Flows as a layer built on the pipeline - Add a namespace note to the 1.0 migration guide
Contributor
|
🔍 Mintlify preview for this branch: https://daily-docs-flows-built-in-framing.mintlify.app |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
Pipecat Flows recently moved from its standalone package/repo into core Pipecat (pipecat-ai/pipecat#4882). Several docs pages still framed Flows as an external add-on you install separately. This PR reframes Flows as built in — it ships with
pipecat-ai, imports frompipecat.flows, and lives in the main repo.Changes
uv add pipecat-ai-flows; show only thepipecat-aiinstall with the note that Flows is included with Pipecat.from pipecat_flows import …→from pipecat.flows import …across guides and API reference.pipecat-ai/pipecat-flowsrepo topipecat-ai/pipecat(examples now underexamples/flows/).reference-server.pipecat.ai/en/latest/api/pipecat.flows.html(same build as base Pipecat) instead of the oldreference-flows.pipecat.ai.pipecat-ai1.5.0, Flows is part of core Pipecat and imports frompipecat.flows; update its examples to the new path. Kept as historical 0.0.x→1.0 content.Kept as-is (by decision)
/pipecat-flows/URL namespace and redirects are unchanged.🤖 Generated with Claude Code