Deploying

Deploying Agents

Deploy an agent to production with agent deploy. This uploads your agent config, tools, and any local files to the platform.

Environments

Deploy to staging and production environments separately. Use agent deploy --env staging for preview deployments and --env production for live.

Rollback

Run agent rollback <deployment-id> to instantly revert to a previous deployment if something goes wrong.

What deploying means

Deploying an agent in Queue means publishing your queue.yaml config — including agent definitions, tool configs, and environment settings — to a specific environment. Deployed agents can be triggered via the API, webhooks, Slack, or CI without needing local access to your config file.

Environments

Queue supports three environments out of the box: development, staging, and production. Each environment has its own deployed agent config, API keys, and integration credentials.

Deploying

queue deploy --env production

This uploads your queue.yaml to the specified environment, validates all agent configs, and makes them available for remote triggering. A deployment ID is returned — keep it for rollback.

Deploy options

--env

Target environment. Defaults to development if omitted.

--agent

Deploy a single agent instead of all agents in the config. Useful for incremental rollouts.

--dry-run

Validate and preview the deployment without actually pushing it. Catches config errors before they reach production.

Rollback

queue rollback <deployment-id> --env production

Instantly reverts to the specified deployment. The previous config is restored within seconds. List recent deployments with queue deployments list.

Deploying in CI

Add a deploy step to your GitHub Actions workflow to auto-deploy on merge to main:

- name: Deploy Queue agents run: queue deploy --env production env: QUEUE_API_KEY: ${{ secrets.QUEUE_API_KEY }}