pipecat create.
pipecat init writes three files:
AGENTS.md— the agent-facing guide (how to build Pipecat apps: scaffold first, check APIs against live sources instead of stale training data, verify with the eval harness). Picked up automatically by coding agents.CLAUDE.md— a one-line import ofAGENTS.mdso Claude Code loads the guide.GETTING_STARTED.md— developer-facing guidance: how to set up the Pipecat Context Hub, write an effective first prompt, and what to expect from a coding session.
pipecat init does not scaffold a project — it makes a project
agent-ready. To scaffold a runnable bot, use pipecat create (the recommended flow is to run pipecat init, then let your coding agent drive pipecat create).Directory to make agent-ready.
pipecat init my-bot targets ./my-bot;
pipecat init . targets the current directory. With no argument, the CLI
prompts for a directory.Overwrite an existing
CLAUDE.md. By default CLAUDE.md is written only when
absent, so a developer’s own file is never clobbered.Behavior
AGENTS.mdandGETTING_STARTED.mdare always (re)written, so re-runningpipecat initrefreshes the guide after a Pipecat upgrade.CLAUDE.mdis preserved if it already exists — pass--forceto overwrite it.- The written
AGENTS.mdends with a provenance footer naming thepipecat-aiversion that wrote it, so a stale guide is detectable and refreshable. - Passing scaffolder flags (e.g.
--name,--bot-type) prints a message redirecting you topipecat createand exits non-zero.
Examples
Prompt for a directory
Make a specific directory agent-ready
Make the current directory agent-ready
Refresh the guide, overwriting CLAUDE.md
Next Steps
Open the project in your coding tool and let the agent take it from here — it readsAGENTS.md and scaffolds the app with pipecat create.
pipecat create
Scaffold a runnable bot — services, pipeline, and deploy path wired up