Slack
Mention @ellipsis in a channel or DM the bot, and an agent picks the conversation up as its prompt and answers in the thread. Configure your responder for the channels and DMs you choose, and let any session post its results back to Slack.
A mention starts a durable conversation in that thread, and replies continue it without mentioning again. The question, the answer, and the pull request it turned into all sit in the same place your team was already discussing it.
A mention, a thread, and the PR it produced
One slack.yaml in your .ellipsis repository defines your responder, with its repositories, model, prompt, permissions, and budget. Choose the channels and DM authors it answers; other conversations use the built-in responder.
ellipsis: kind: slack name: supportslack: channels: [' #support']session: harness: type: codex instructions: Answer from the code and cite relevant files. environment: repositories: - name: api-repoOne file defines your Slack responder
Slack is an output, not only an input. Any session on a connected workspace can read a channel for context and post its result where the team reads, so a nightly job's findings arrive as a message on Monday morning instead of sitting in a log.
Slack tools available in every session