Slack is config-gated: it is only available when the deployment has Slack OAuth credentials configured. If you do not see Slack in Settings → Connections or the CLI commands return errors, the deployment has not enabled it. See Integrations.
Prerequisites
A route targets an Aether project that has a linked GitHub repo — that is where the agent’s work lands. Connect GitHub and import a repo first; see GitHub integration.Connecting Slack
- Web
- CLI
Go to Settings → Connections → Slack and click Connect to authorize Aether for your Slack workspace.
Listing Channels
Routes are keyed by channel, so look them up first:Creating a Route
A route maps a Slack channel to an Aether project.--channel-id and --channel-name must be provided together; omit both to pick a channel interactively. Add --private when supplying a private channel by ID. --aether-project accepts a project ID or short prefix and defaults to your selected project; it must be a project with a linked repo. New routes are enabled by default — pass --enabled false to create one paused.
Starting Tasks from Slack
In a routed channel, post a message mentioning @Aether to start a task. Aether replies in that message’s thread and posts its progress, result, project, task link, and PR link there as the task runs. Replycancel, stop, or abort in the thread to cancel the task.
If your Slack user’s direct messages are wired up (shown by aether slack status), Aether can also deliver your task notifications as Slack DMs.
Managing Routes
enabled flag lets you pause a route without deleting it.
Disconnecting Slack
API
The Slack endpoints are part of the frontend/CLI API surface, not the versioned/v1 API, and are config-gated — see the API overview. Browse the operations under the Slack group, for example list routes and create a route. The full CLI reference is at aether slack.