CLI¶
PyFlue exposes the pyflue command.
pyflue init¶
Create a new project:
Overwrite an existing directory:
Generated files:
pyflue run¶
Run one prompt:
Use a named session:
Enable sandbox writes and shell:
Print stream events:
pyflue skill new¶
Create a new Markdown skill:
pyflue add¶
Print connector setup instructions for a coding agent.
List available connector guides:
Show copyable agent commands:
Print the full guide:
Build a custom sandbox connector from provider docs:
The command does not install hidden dependencies. It prints a clear guide that your coding agent can apply to your project.
pyflue build¶
The default target is Docker/FastAPI.
Available targets:
| Target | Status | Generated files |
|---|---|---|
docker |
Implemented | Dockerfile, app.py |
github-actions |
Implemented | .github/workflows/pyflue-agent.yml |
gitlab-ci |
Implemented | .gitlab-ci.yml |
railway |
Implemented | Dockerfile, app.py, railway.json |
render |
Implemented | Dockerfile, app.py, render.yaml |
fly |
Implemented | Dockerfile, app.py, fly.toml |
vercel |
Implemented | Dockerfile, app.py, vercel.json |
netlify |
Implemented | Dockerfile, app.py, netlify.toml |
cloudflare |
Partial | wrangler.toml |
pyflue dev¶
Start the local development server with reload:
The server exposes:
GET /health
GET /agents
POST /agents/{name}/{agent_id}
POST /prompt/{agent_id}
POST /prompt/{agent_id}/events
pyflue deploy¶
Generate deployment artifacts and a deployment manifest:
Select a target:
For supported provider CLIs, PyFlue runs the provider command when the CLI is
installed and you are logged in. For other targets, it writes project files and
.pyflue/deploy.json with the next step.