Slack

Connect a workspace from Integrations > Slack in the dashboard. Invite Ellipsis to private channels it needs to access.

Agent access

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

The connection also supplies workspace channels and members for configuration. Choose the operations channel from the integration's dashboard settings.

Mention routing

Slack mentions use slack.yaml at the root of the organization's .ellipsis repository. The file defines one responder and selects the channels and direct messages it answers.

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

slack:
  channels: ['#engineering', '#support']
  direct_messages: ['*']

session:
  codex:
    prompt: |
      Read the code before answering. Cite the relevant files and
      functions, and keep replies short.
  environment:
    repositories:
      - name: api-repo
  permissions:
    github:
      permissions: read_only
  budget:
    session: 2

This responder answers mentions in #engineering and #support, plus all direct messages. Other channels use the built-in responder.

Field	Behavior
`slack.channels`	Channel names, with or without `#`. `['*']` matches all channels.
`slack.direct_messages`	Linked GitHub logins, such as `['priya-shah']`. `['*']` matches all DM authors, including people without a linked GitHub account.
`session`	The responder's harness, prompt, environment, permissions, skills, and budget, in the same structure as automation schema reference. An environment can also be a saved environment name.

Set at least one of slack.channels or slack.direct_messages. Wildcards apply separately to channels and DMs and cannot be mixed with names in the same list. Channel names and GitHub logins match without regard to case.

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

This routing is separate from a slack_channel automation trigger, which responds to channel creation rather than messages.

Access changes

Removing the connection prevents future Slack access. Review the integration's agent access setting before granting tools broadly to sessions.

Agent access

Mention routing

Access changes

On this page