Integrations

Aether integrates with four third-party services. Connecting one authorizes Aether to read from it and, for Sentry, Linear, and Slack, to spawn tasks in response to events from it. Each connection is per user and is managed from the dashboard or the CLI.

​

What connecting does

GitHub is the foundation — Sentry, Linear, and Slack routes all target an Aether project that has a linked GitHub repo, since that is where the agent’s work lands.

​

Routes spawn tasks

Sentry, Linear, and Slack share the same model: you create routes mapping a source object to an Aether project, and matching events spawn tasks in that project.

• Sentry routes map a Sentry project to an Aether project, on or off. A new error in a routed project opens a fix task in that project.
• Linear routes map a Linear team (optionally a specific project within it) to an Aether project. Matching issues open tasks; results return as Linear comments.
• Slack routes map a Slack channel to an Aether project. Messages in routed channels open tasks; task updates publish back to the Slack thread.

Each route has an enabled flag so you can pause it without deleting it. Manage routes from the CLI (aether sentry, aether linear, aether slack) or the dashboard.

​

Availability is config-gated

GitHub is always available. Sentry, Linear, and Slack are only available when the deployment has the corresponding OAuth credentials configured. If those credentials are unset, the integration is absent entirely — its connect flow, routes, and webhooks are not registered. If you do not see one of these integrations, the deployment you are on has not enabled it.

​

Connecting