Answer @ellipsis mentions
Route mentions on GitHub, Slack, and Linear to an agent.
Mention @ellipsis where the work lives and Ellipsis answers in the thread, with the conversation as context and the run's tools available for code changes. This works with no config at all: a built-in responder answers every mention.
Add a mention trigger to take over mention handling with your own agent, controlling which sandbox repositories, model, and limits those runs use:
ellipsis:
version: v1
name: Mentions
description: Answers @ellipsis on GitHub, Slack, and Linear
triggers:
- type: mention
platforms: [github, slack, linear]
sandbox:
repositories:
- name: splitshift-web
- name: splitshift-api
limits:
run: 2.00A mention agent needs no system prompt: its response is built from the conversation it was mentioned in. If several enabled configs claim the same platform, the oldest one answers.
Platforms
platforms scopes where this agent answers. Leave it empty to answer everywhere.
| Platform | Where it answers |
|---|---|
github | Pull request and issue comments. |
slack | App mentions, direct messages, and thread replies. |
linear | Issue comments. |
Where mentions work
| Surface | Context the run gets |
|---|---|
| GitHub pull request comments | The pull request, repository, and triggering comment. |
| GitHub issue comments | The issue, repository, and triggering comment. |
| Slack messages and app mentions | The Slack thread and any linked GitHub identity. |
| Linear issue comments | The Linear issue and comment thread. |
On GitHub, @ellipsis is detected anywhere in the comment. On Linear, the comment must lead with @ellipsis so a mirrored GitHub thread does not summon Ellipsis twice. In a Slack thread that already mentioned Ellipsis, replies continue the run without mentioning it again.
A GitHub mention adds the PR's or issue's repository to the sandbox automatically, so a PR comment mention can read that PR's code even if the config lists other repositories. Slack and Linear mentions have no repository of their own; those runs clone the repositories the config declares.
What to ask
Mentions fit work that needs repository context or integration actions:
@ellipsis why does the shift-trade expiry migration need a backfill?@ellipsis fix the double-booking race from this thread and open a PRThe first gets an answer in the thread grounded in the migration code. The second produces a reply linking the pull request the run opened.
Next
Mentions are one of three trigger types; the same agent can also declare cron and react triggers.