Atlarix in Slack

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.

Mention @Atlarix in a channel, or DM it:

• acme/web: add rate limiting to the login endpoint — starts a task in that repository.
• repo acme/web — sets your default repository; after that, just describe the task.
• [core-2] acme/web: … — picks an Atlarix Core model for that task. Without one it's Atlarix Auto.
• help — what it can do.

Atlarix answers in the thread when it starts and again with the pull request: what changed, what it cost, and an Approve & merge button. Close closes the pull request without merging.

• Atlarix in Slack is a paid feature. It runs on Atlarix models, billed to the Atlarix balance of the person who asked: Pro's included usage, then credit.
• There is no own-key option in Slack. To run a task on your own API key, start it at atlarix.dev/cloud.
• The runner is your GitHub Actions minutes, free on public repositories.

• 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.

• 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 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.