Cloud agent

    Ask Atlarix for work from Slack or atlarix.dev. It runs in your repository's own GitHub Actions and brings back a pull request.

    How it works

    You ask for work — in a Slack DM (owner/repo: add rate limiting to the login endpoint) or at atlarix.dev/cloud. Atlarix starts a workflow in that repository's GitHub Actions, the agent makes the change and runs your tests, and a pull request comes back with an Approve & merge button.

    • Nothing merges until the person who asked approves it.
    • Merging is the end of our part: your existing deploy pipeline (Vercel, Netlify, Actions) deploys it as it would any merge.
    • Your computer can be off. The desktop app is not involved.

    Set it up

    1. 1Go to atlarix.dev/cloud and install the Atlarix Cloud Agent GitHub App on the repositories it may work on.
    2. 2Press Add workflow next to each one. That opens a pull request adding .github/workflows/atlarix.yml; merge it.
    3. 3Optionally press Add to Slack, then DM Atlarix. The first time, it sends a button to connect your Atlarix account.

    What it costs

    • The runner is your GitHub Actions: free on public repositories, your included minutes on private ones.
    • On your own API key, a run is free: save the key as the repository secret ATLARIX_PROVIDER_KEY and set ATLARIX_PROVIDER and ATLARIX_MODEL as repository variables, then choose My own API key when you start it.
    • On an Atlarix model, model usage is billed to your Atlarix balance (Pro's included usage or credit): Atlarix Auto, which picks the model for each step, or any paid Atlarix Core model. Free Auto does not cover cloud runs.
    • Each finished run shows what it cost.

    What it can reach

    • No secret is added to your repository. The runner proves where it is running with GitHub's own OIDC token, and only the Atlarix workflow in that repository can claim a job.
    • The agent's model access is a token for that one job. It stops working when the job ends.
    • The credential that can push is fetched only after the agent has finished, and it covers that one repository.
    • In Slack, work is billed to the account linked to the person who asked, and only that person can approve it.

    Preparing the environment

    If your tests need more than the checkout — dependencies, a database — add .atlarix/cloud-setup.sh to the repository. It runs before the agent starts.

    ← Back to Docs