Skip to main content
Preview: AI Builder Portal is in preview. Features and capabilities are under active development and may change.
Autonomous agents pick up issues from your project tracker, work on them in isolated cloud environments, and open pull requests - without human intervention. They use the same blueprint and governance infrastructure as workspaces, but operate autonomously. Linear and Jira are supported as project trackers. A GitHub Issues integration is planned.

​
How It Works

When a user triggers the agent on an issue - by @mentioning or assigning it in Linear, or by assigning it to the agent’s user in Jira - the agent claims it, launches a workspace, writes the code, opens a pull request, and shuts down. Progress is reported back on the issue in real time.

​
Agents vs Workspaces

Autonomous agents and workspaces share the same underlying infrastructure but serve different workflows.

​
Supported Runtimes

Each agent blueprint specifies which AI coding runtime to use. The runtime determines the CLI tool that drives the agent inside the workspace.

Claude Code

Anthropic’s coding agent. Runs claude -p with the issue description as the prompt.

OpenCode

Open-source coding agent. Runs opencode run to process the issue autonomously.

Codex

OpenAI’s coding agent. Runs codex --full-auto for fully autonomous operation.

Gemini CLI

Google’s coding agent. Runs gemini -p with the issue context as input.

Cursor CLI

Cursor’s agent mode. Runs cursor-agent to resolve the issue.

​
Shared Infrastructure

Autonomous agents run on the same Kubernetes cluster as workspaces. They use the same split architecture - the portal orchestrates agent runs from rde.qovery.com, while the agent containers execute on your infrastructure. The same security model applies: no inbound ports, outbound-only TLS/gRPC tunnels, and all code stays on your cluster. For details on the underlying infrastructure, see Architecture and Security & Data Residency.

​
Supported Project Trackers

Both trackers connect via OAuth and auto-refresh their tokens. You configure which tracker an agent blueprint uses in the Create Agent Blueprint wizard.
  • Linear - trigger agents by @mentioning or assigning them on issues. The agent responds with a real-time plan and progress updates visible directly in Linear as agent activities. See Linear Integration.
  • Jira - trigger agents by assigning an issue to the agent’s Jira user. Progress is reported as issue comments and workflow status transitions. See Jira Integration.
A GitHub Issues integration is planned. If you need a specific integration, contact the Qovery team.

​
Next Steps

Getting Started

Set up your first autonomous agent with Linear integration.

Agent Blueprints

Configure blueprints that define how agents run.

Managing Runs

Monitor agent runs, review results, and troubleshoot failures.

Linear Integration

Connect Linear, configure labels, and manage issue routing.

Jira Integration

Connect Jira, map statuses, and trigger agents by assignment.