The polpo deploy command syncs your local .polpo/ directory to Polpo. It uploads agent configurations, teams, missions, playbooks, skills, memory, and vault credentials.
Prerequisites
Your project must be linked before deploying. Use either:
# New project (handles login, project creation, scaffolding)
npx @polpo-ai/cli create
# Existing project
npx @polpo-ai/cli link --project-id <uuid>
Usage
Options
| Flag | Description |
|---|
--dir <path> | Path to .polpo/ directory (defaults to .polpo) |
--yes | Skip confirmation prompt |
--include-tasks | Include task definitions |
--include-runs | Include run history |
--include-sessions | Include session data |
--all | Include tasks, runs, and sessions |
What gets deployed
Always included:
| Resource | Source |
|---|
| Agents | .polpo/agents.json |
| Teams | .polpo/teams.json |
| Memory | .polpo/memory.md + .polpo/memory/ |
| Missions | .polpo/missions/ |
| Playbooks | .polpo/playbooks/ |
| Skills | .polpo/skills/ |
| Vault | .polpo/vault.enc |
| Resource | Flag |
|---|
| Tasks | --include-tasks |
| Run history | --include-runs |
| Sessions | --include-sessions |
| Everything | --all |
Deploy flow
Check project link
The CLI reads .polpo/polpo.json to identify the target project. If missing, it prompts to create or link one.
Scan .polpo/
All files in the .polpo/ directory are scanned and categorized.
Display summary
A summary of what will be deployed is printed for review.
Confirm
You’re prompted to confirm (skip with --yes).
Deploy
Files are uploaded to the project’s subdomain ({project}.polpo.cloud).
Report
A deployment report is printed with success/failure status for each resource.
Deploying overwrites the remote state for all included resource types. It does not merge — the remote configuration is replaced with your local .polpo/ contents.
