Skip to main content
polpo deploy reads a local .polpo/ configuration and reconciles its resources with a Polpo Cloud project. polpo create creates and links a project, scaffolds .polpo/, and performs the initial deploy:
To link an existing project and pull its current resources:
The project ID and generated 20-character slug are stored in .polpo/project.json.

​
Usage

There is no run-history deploy flag. --all does not add run history.

​
Environments

Each project has isolated Development and Production runtimes. The CLI defaults to Development on every invocation. Production therefore requires polpo deploy --prod or polpo deploy --env production; the previous command, Git branch and NODE_ENV never change that default. Both environments use the same local .polpo/ definition tree, but deploy independently. Deploying one does not copy the other environment’s database, files, memory, Connections, Channels, BYOK keys or runtime settings. The selected environment must already be available and the credential must be authorized for it. A mismatch fails instead of retrying against another environment.

​
Resources

The default deploy covers resources represented by the local configuration:
  • teams and agents
  • Agentic Loops
  • shared and agent-specific memory
  • missions and playbooks
  • skills and custom tools
  • schedules
  • vault entries
  • agent avatars
Tasks and sessions require their explicit flags because they are operational data rather than normal project configuration.

​
Conflict behavior

The CLI compares supported resources with their remote counterparts, skips identical data, and reports conflicts. In an interactive deploy you can choose how to resolve a conflict; --force chooses the local version. Deploy is not a blanket replacement of all remote state. A missing local file does not generally delete the corresponding remote resource. Use the resource API or dashboard when an explicit remote deletion is required.

​
Local LLM keys

Provider credentials are configured explicitly in each environment with the BYOK command or dashboard. Deploy does not discover or upload model keys from the process environment or .polpo/.env; --yes and --force do not change that boundary. Recognized variables include ANTHROPIC_API_KEY, OPENAI_API_KEY, GEMINI_API_KEY, XAI_API_KEY, GROQ_API_KEY, OPENROUTER_API_KEY, MISTRAL_API_KEY, CEREBRAS_API_KEY, MINIMAX_API_KEY, HF_TOKEN, and Azure credentials.
.env.local, created by polpo create for POLPO_URL and POLPO_API_KEY, is separate from .polpo/.env, which a local runtime can use for provider credentials. Deploy does not upload those credentials.