Resources

Avrea for agents

Find the setup guide, command reference or product facts your agent needs for the task.

Read this page as Markdown Website index Documentation index

Start with your task

Run a GitHub Actions job on Avrea

GitHub Actions keeps orchestrating the workflow; Avrea runs the job. Start with the GitHub App installation and a runner label that matches the job’s OS, architecture and size. Check the repository’s requirements before proposing a change.

Investigate a slow or failed job

Use run history, step logs and resource metrics to identify the job and the failing or slow step. The CLI reference documents structured output and the options supported by each command.

Configure caching for a build

Choose the cache integration for the build tool, then check cache hits and the time spent restoring and saving data. Package downloads, build outputs and Git checkout have separate configuration and behavior.

Work in a sandbox

Read the sandbox guide before creating a VM. It covers organization access, available machines, repository setup, connection methods and time limits. Check the supported platforms for pause and fork, and the lifetime of a paused disk.

Compare cost and performance

Match runner size, operating system and architecture. Keep list rates separate from credits and discounts. For benchmarks, retain the workload, cold or cached state and absolute run times when citing a result.

Choose another Avrea product

Avrea CI schedules and executes workflows directly; it is separate from using Avrea runners with GitHub Actions. Avrea CI and Avrea AI have access-request paths. For Git Mirroring setup, talk to an engineer about your connected repositories and locations.

Give your agent a concrete starting point

For a runner migration, ask it to inspect the workflow and propose a change first. The repository owner handles GitHub App installation and access approval.

Review a runner migration

Read https://docs.avrea.com/getting-started/ and inspect this repository’s GitHub Actions workflows. Identify a compatible build or test job and propose the smallest runner-label change. Explain prerequisites and the runner size comparison. Show the diff before changing files or running workflows.

Read the source that fits the question

Use the product docs for setup, supported options and limits. Use the pricing page for current list rates and the linked benchmark study for measurement conditions. Account-specific access and billing belong in your organization’s console.

llms.txt links to the website’s product, pricing and reference pages.
Docs llms.txt links to setup and command documentation.
llms-full.txt contains the full website text. Use an individual page when you only need one topic.

Public website pages also have a Markdown copy: use /pricing.md for /pricing, or /index.md for the homepage. Each page links its copy in the HTML head.

Reviewed 11 November 2026. Need help with access or setup? Contact Avrea.