Agent Blueprints

​

Overview

An agent blueprint is a blueprint with autonomous mode enabled. It defines which AI runtime to use, which repositories to clone, and how to connect to your project tracker (Linear or Jira). When a matching issue is triggered, the system launches a workspace from this blueprint and runs the agent autonomously. Agent blueprints share the same underlying infrastructure as workspace blueprints - lifecycle states, target cluster selection, and Qovery environment mapping all work the same way. See Blueprint Management for those shared concepts.

​

Workspace vs Agent Blueprints

​

Configuration Reference

These settings are specific to agent blueprints. They control which runtime executes the agent, which tracker the agent connects to, and how many runs can execute concurrently. Tracker-specific field names and semantics differ slightly between Linear and Jira. See Linear Integration and Jira Integration for the exact mappings.

​

Runtime Details

Each agent blueprint specifies one AI coding runtime. The runtime determines which CLI tool runs inside the workspace and which API key environment variable is required.

​

Resource Defaults

Agent blueprints created through the wizard use these default resource allocations. You can adjust them under Advanced during creation or by editing the blueprint later. The target cluster defaults to the first non-production cluster in your organization.

​

Git Provider Support

Agent blueprints support three git providers for cloning repositories, pushing branches, and creating pull requests: The provider is detected automatically from the repository URL configured in the blueprint. The agent template handles authentication, branch creation, and PR creation for all three providers.

​

Official Agent Template

Agent blueprints created through the wizard use the official agent template (ghcr.io/qovery/autonomous-agent-template:latest) as the base Docker image. This image includes all five AI runtimes, development tooling, and the autonomous entrypoint script. You can extend the template with project-specific dependencies by creating a custom Dockerfile that builds on top of the official image. See Agent Template for details on customization, environment variables, and the governance proxy.

​

API Key Management

The API key for the selected runtime is stored as an environment variable on the blueprint’s Qovery environment. Different runtimes use different environment variable names - see the Runtime Details table for the mapping. The key is set during blueprint creation when you enter it in the wizard. To update it later:

1. Open the Qovery Console.
2. Navigate to the project and environment backing the agent blueprint.
3. Edit the environment variables and update the relevant API key.

​

Editing Agent Blueprint Settings

New agent blueprints are created from the Admin > Agent Blueprints page using the Create Agent Blueprint wizard. This page lists all agent blueprints, each tagged with a Linear or Jira provider badge. To modify an existing agent blueprint:

1. Navigate to Admin > Blueprints in the portal.
2. Click the blueprint name to open its settings.
3. Select the Autonomous tab.

From this tab you can:

• Enable or disable autonomous mode
• Change the AI runtime
• Update the tracker’s team/project and state/status mappings
• Adjust concurrency limits and run timeout

If the portal does not have the selected tracker connected via OAuth, a warning is displayed prompting you to connect it first. See Linear Integration or Jira Integration for setup instructions.

​

Next Steps