Linear

Connect a workspace from Integrations > Linear in the dashboard.

Agent access

Agent sessions using Linear tools require a Codex model with MCP support. See Models and MCP configuration.

The integration exposes connected teams and settings for configuration.

Mention routing

Linear mentions use linear.yaml at the root of the organization's .ellipsis repository. The file defines one responder and selects the teams and projects it answers in.

ellipsis:
  version: v1
  kind: linear
  name: linear-helper

linear:
  teams: [ENG]
  projects: [Website]

session:
  codex:
    prompt: |
      Read the issue and relevant code before answering. When asked
      for a fix, implement it, run the tests, and open a pull request.
  environment:
    repositories:
      - name: api-repo
      - name: web-repo
  budget:
    session: 5

This responder answers mentions on issues belonging to the ENG team or the Website project. Other issues use the built-in responder.

Field	Behavior
`linear.teams`	Team keys or names, such as `ENG` or `Engineering`. `['*']` matches every issue.
`linear.projects`	Project names. Wildcards are not supported here; use `linear.teams: ['*']` for every issue.
`session`	The responder's harness, prompt, environment, permissions, skills, and budget, in the same structure as automation schema reference.

Set at least one of linear.teams or linear.projects. Names match without regard to case. A team wildcard cannot be mixed with team names.

Linear issues have no GitHub repository of their own. session.environment must name the repositories the responder needs, or reference a saved environment containing those repositories.

The default-branch version is live. Invalid edits retain the last successfully synced configuration. Missing or disabled files and issues outside the configured filters use the built-in responder. A copy outside the organization's .ellipsis repository does not configure Linear.

Issue events

The automation schema includes trigger.linear_issue for newly created issues. This is separate from mention routing and follows the same capability restrictions.

Agent access

Mention routing

Issue events

On this page