Opening GitHub…Opening Discord…

    Atlarix in Slack

    Add Atlarix to Slack, connect your account, and ask for changes to a repository in a DM or by mentioning @Atlarix.

    Set it up

    1. 1Press Add to Slack on atlarix.dev/slack (or on your account page) and allow it in your workspace.
    2. 2On atlarix.dev/cloud, install the Atlarix Cloud Agent GitHub App on the repositories it may work on, and merge the workflow pull request it opens for each.
    3. 3DM Atlarix in Slack. The first time, it sends a Connect Atlarix button: it opens atlarix.dev, where you confirm which Atlarix account pays for work you ask for in Slack.

    Asking for work

    Mention @Atlarix in a channel, or DM it:

    • acme/web: add rate limiting to the login endpoint — starts a task in that repository.
    • ask acme/web: how does sign-in work? — an answer about the code, with no pull request.
    • review acme/web#12 — Atlarix Reviewer reviews that pull request and posts a summary in the thread.
    • repo acme/web — sets your default repository; after that, just describe the task.
    • help — what it can do.

    Reply in a task's thread to take the next turn: the same repository and, while it's open, the same pull request, with what came before. In a channel, mention @Atlarix in the reply. Atlarix never stops mid-run to ask; anything it needs to know is in its reply, and your answer is the next turn.

    Attach screenshots or files and the run gets them. Tag teammates and Atlarix opens a private channel for the task with you and them in it.

    Atlarix keeps one status card in the thread: queued, each step as it happens, then the pull request with what changed, what it cost, and an Approve & merge button. Close closes the pull request without merging. Tasks from Slack run on the repository's own API key when one is saved on atlarix.dev/cloud, otherwise on Atlarix Auto.

    What it costs

    • Atlarix in Slack is a paid feature. Tasks and questions run on Atlarix Auto, billed to the Atlarix balance of the person who asked: Pro's included usage, then credit. So do messages that aren't an explicit owner/repo: task, which Atlarix Auto reads to decide what you meant.
    • The runner is your GitHub Actions minutes, free on public repositories.

    Who can do what

    • Each person connects their own Atlarix account. Work is billed to whoever asked.
    • Only the person who asked can press Approve & merge, or Close.
    • A teammate in the same channel can't start work on your account or approve your pull request.

    What the app reads and keeps

    • It reads only messages addressed to it: DMs to Atlarix, and messages that mention @Atlarix. Not other channel messages, not channel history.
    • It keeps the workspace's bot token (encrypted), each connected person's link and default repository, and each task's record.
    • Removing the app from the workspace deletes the workspace's data and everyone's link. Disconnect yourself any time from your account page.
    • The full details are in the privacy policy, under The Atlarix app for Slack.

    If nothing comes back

    If a task says GitHub didn't start the workflow, open the repository's Actions tab: usually the account is out of Actions minutes or over its spending limit, or Actions is turned off for the repository, or the workflow file isn't on the default branch yet.