Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.replicas.dev/llms.txt

Use this file to discover all available pages before exploring further.

Replicas integrates with Slack as a bot you can mention in channels or message directly. Either way, it spawns a workspace to complete the work and replies in the thread.

​
Setup

  1. Go to Integrations settings
  2. Click Connect Slack and authorize for your workspace
  3. Invite @Replicas to the channels where you want to use it (or open a DM with the bot)
If you connected Slack before DM support shipped, re-authorize from the same Integrations page so the new im:* and mpim:* scopes are granted. Until then DMs will not deliver to the bot. Ensure you have at least one repository configured before mentioning Replicas.

​
How It Works

When you mention @Replicas in a channel:
  1. Replicas adds an 👀 reaction to acknowledge your message
  2. If multiple environments are configured, you’ll see a dropdown to select which one to work in
  3. A workspace is created for the task in that environment
  4. The agent sends a brief acknowledgment, then works on your request
  5. When done, the agent replies in the thread with results (typically a PR link)

​
Direct Messages

You can also DM the bot 1:1 or in a group DM. Every message you send to Replicas in a DM is treated as a task, so you do not need to type @Replicas. The same flow applies as in channels: Replicas reacts, picks an environment, creates a workspace, and replies in a thread on your message. Replies inside that thread route to the same workspace, see Thread Conversations. Environment selection works identically, see Environment Selection.

​
Environment Selection

Workspaces are created inside an environment, and the env’s binding determines which repository or repository set gets cloned. If your organization has multiple environments, you can:
  • Use the dropdown: Replicas will prompt you to select an environment
  • Specify inline: Add [env:name] to your message (e.g., @Replicas [env:backend] add a login page)
The [env:name] syntax matches against environment names. Org admins can also set a default environment under Settings → Organization to skip the prompt entirely.

​
Thread Conversations

Each Slack thread is linked to one workspace. Follow-up mentions in the same thread route to the same workspace, so the agent remembers previous context. On follow-ups, only new messages are sent to the agent rather than the full thread history, keeping the context focused. If the workspace is deleted and you mention @Replicas again in that thread, a new workspace is automatically created.

​
Context

The context provided to the agent includes:
  • Your message (with bot mention stripped)
  • Thread history — for the first message, the full thread context is included; for follow-up messages, only new messages since the agent last responded are sent
  • Channel name
  • User names of participants

​
Intended Usage

Slack works best for quick requests and iterative conversations:
  • Start tasks with a brief description
  • Follow up in the same thread to refine or add requirements
  • The agent responds directly in Slack, making it easy to share progress with your team
Add /plan in your message to request a planning-only response with a plan link. See Plan Mode.