Linear is config-gated: it is only available when the deployment has Linear OAuth credentials configured. If you do not see Linear 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 Linear
- Web
- CLI
Go to Settings → Connections → Linear and click Connect to authorize Aether to access your Linear organization.
Listing Teams and Projects
Routes are keyed by Linear team and (optionally) project ID, so look those up first:Creating a Route
A route maps a Linear team (and optionally one project within it) to an Aether project. Omit the Linear project to match every issue in the team.--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.
What Happens on an Issue
When a matching Linear issue triggers Aether, the agent opens a task seeded from the issue’s identifier, title, description, labels, and recent comments, with instructions to implement the fix, run checks, and open or update a PR. Progress and the final result post back to the Linear issue as comments and agent-session activities, including links to the Aether task and the pull request.Managing Routes
enabled flag lets you pause a route without deleting it.
Disconnecting Linear
API
The Linear 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 Linear group, for example list routes and create a route. The full CLI reference is at aether linear.