Alpha. Agent Tasks is in early development and not yet generally available. Capabilities and setup will change before release.
Overview
Identifies build and deployment optimization levers and their expected gain, then opens a PR with the proposed change and/or updates the build configuration in Qovery directly. It never merges a fix on its own.
How It Works
To find concrete ways to make builds and deployments faster and cheaper, the agent:
- Inspects the service’s build setup: Dockerfile, dependency installation, layer caching, image size, and the build/deploy configuration in Qovery.
- Identifies optimization levers, for example better layer ordering and caching, multi-stage builds, smaller base images, pruning unused dependencies, or parallelisable steps.
- For each lever, estimates the expected gain (build time, image size, or cost) and the risk.
- Opens a PR with the proposed changes to the build configuration, and/or updates the build configuration in Qovery directly.
- Summarises what it changed, the expected gain, and anything that needs a human decision. It never merges, the human always stays the gate.
Setting It Up
- Context: add the service’s Git repository so the agent can inspect the Dockerfile and build setup.
- Access: add the Qovery MCP server manually (
https://mcp.qovery.com/mcp). A read-only API Policy Token is enough to read the build/deploy configuration and propose changes via PR. Use one with write permissions instead if the agent should update Qovery directly.
- Resources and environment variables: see Configuration for the general settings shared by every agent task.
Triggering It
Add a schedule trigger, for example weekly, to periodically review build performance, or trigger it from a webhook. See Automations for how triggers and outputs work in general.
