Skip to main content
Aether connects to four third-party services and lets you bring your own coding-agent provider credentials. Each connection is per user and managed from Settings → Connections in the web app or from the aether CLI. This page is the practical hub; for the conceptual model of how integration events spawn tasks, see Integrations (concepts).

​
Third-party integrations

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. Connect GitHub and import a repo first.

​
Availability is config-gated

GitHub is always available. Sentry, Linear, and Slack are only available when the deployment has the matching OAuth credentials configured — the Sentry app credentials, the Linear client ID/secret/webhook secret, or the Slack client ID/secret/signing secret. When those are unset, the integration is absent entirely: its connect flow, routes, and webhooks are never registered. If you do not see one of these integrations, the deployment you are on has not enabled it.

​
Agent connections

Aether ships three selectable agent providers — Codex (default), Claude Code, and OpenCode. Claude Code and Codex tasks run on Aether inference or a held connection; OpenCode needs a held connection. Connections are named, and each harness has its own default connection. See Agent connections.

​
Where integrations live in the API

Integration and provider-auth endpoints are part of the public API and, for Sentry/Linear/Slack, may be config-gated. See the API overview.

​
Connect

GitHub

Install the App, import a repo, push changes, review PRs.

Sentry

Route Sentry projects to Aether projects and auto-fix new errors.

Linear

Route Linear issues to Aether projects.

Slack

Route Slack channels to Aether projects.