Linear

Connect Linear, answer Ellipsis mentions on issues, and give sessions Linear tools.

Ellipsis answers mentions on Linear issues and gives sessions Linear tools.

Answer a mention

  1. Connect a workspace from Integrations > Linear in the dashboard.
  2. Mention Ellipsis with a question in a comment on an issue.

Agent access

A session gets Linear tools when its environment lists linear under mcp_servers, or when it starts from Linear. A session that lists linear while Linear isn't connected fails at start.

Mention routing

Mention Ellipsis in a comment on a Linear issue, picking it from the mention list, to start a session. Ellipsis answers in that comment's thread, and replies in the thread continue the same session. A typed @ellipsis starts nothing. If Ellipsis isn't in the mention list, reconnect Linear from Integrations > Linear. Without a linear.yaml, the built-in handler answers. To customize it, put linear.yaml at the root of your organization's .ellipsis repository:

1
ellipsis:
2
kind: linear
3
name: linear-helper
4
5
linear:
6
teams: [ENG]
7
projects: [Website]
8
9
session:
10
codex:
11
model: gpt-6-sol
12
prompt: |
13
Read the issue and relevant code before answering. When asked
14
for a fix, implement it, run the tests, and open a pull request.
15
environment:
16
repositories:
17
- name: api-repo
18
- name: web-repo
19
budget:
20
session: 5

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

Set at least one of linear.teams or linear.projects. Don't mix '*' with team names. Names match regardless of case.

Linear issues aren't tied to a repository, so list the repositories the handler needs in session.environment, or name a saved environment that has them.

The default-branch version is live, and an invalid edit keeps the last valid one. Set ellipsis.enabled: false, or delete the file, to go back to the built-in handler. Only the copy in the .ellipsis repository counts.

Issue events

To run an agent whenever someone creates an issue, use a linear_issue trigger.

Fields

Identifies the file.

Which issues this handler answers. Set at least one of teams or projects; don't mix '*' with team names.

Works like an agent's session block.

On this page

Schedule a demo