Setup
- Go to Organization → Integrations
- Find Slack, click Install, and authorize for your workspace
- Invite @Replicas to the channels where you want to use it (or open a DM with the bot)
#talk-to-replicas channel, adds the person who authorized the connection, and saves it as your organization’s default Replicas channel. If that public channel already exists, Replicas joins and reuses it. If its name is reserved by an archived or inaccessible channel, Replicas tries numbered names such as #talk-to-replicas-2.
Replicas posts a short introduction after setup. Reconnecting does not repeat a delivered introduction. This channel can also receive changelog updates sent by the Replicas team.
Reconnecting verifies the saved channel, restores the bot’s membership if needed, and replaces missing or archived defaults. If channel setup fails, reconnect to retry.
The Slack app requires the channels:manage and channels:join bot scopes for channel setup. Existing connections can reconnect to grant these permissions and set up their default channel.
Managers reply under their own name and icon with the chat:write.customize scope. Connections made before it was added post as Replicas until you reconnect.
When a thread keeps tagging another coding agent, Replicas may offer to help, at most once a week and twice per person. React 👎 to the offer and Replicas stops offering in your workspace. This uses the reactions:read scope, so connections made before it was added need to reconnect for the 👎 to work.
If you connected Slack before DM or task-fork support shipped, re-authorize from the same Integrations page so the new im:*, mpim:*, and commands scopes are granted. Until then DMs or the Fork task shortcut may not be available.
Ensure you have at least one repository configured before mentioning Replicas.
Personal Account Connection
Connect your Slack account from Personal → Connections to link your Slack user ID to your Replicas account. Replicas then uses your personal defaults and credentials even when your Slack email differs from your Replicas email. Email matching remains a fallback for members who have not connected an account. An administrator must add Slack’sopenid, email, and profile User Token Scopes to the Replicas Slack app once before members can authorize personal connections.
Tell Replicas how to behave
There’s no settings page: ask @Replicas in plain words, in any channel or DM. For example:@Replicas only reply here when someone tags you@Replicas file bugs in Linear and post them in #triage@Replicas be more proactive in #eng@Replicas use Codex for Slack tasks
@Replicas what can I change here? to see what applies to a channel and its current values.
Proactivity
Replicas reads new messages in the channels it’s in and decides when to help. Ask it to change how much it speaks up:
New connections start at Low. The level applies to every channel unless the channel has its own. A channel can also have its own instructions or a preset (Customer, Triage, Internal, or one you ask Replicas to create). Channels shared with another company through Slack Connect follow shared-channel defaults: a level (Mentions only unless an admin changes it), a preset, instructions, and silent mode. They apply to every shared channel without its own settings, including ones Replicas joins later.
Any member can quiet a channel, change its instructions, or manage presets. Only admins can change the level for every channel, raise a channel above Mentions only, turn on silent mode, change shared-channel defaults, start Linear triage for a team, or change the agent defaults for Slack tasks.
When Replicas has to be tagged for something it skipped, or someone is annoyed that it jumped in, it offers once to raise or lower that channel’s level. The first time someone tags it in a channel, it adds a one-line tip that you can tell it how to act there.
Replicas reads channels only once a coding agent is connected. Until then, @mentions start a task as described below.
Silent mode
In a channel in silent mode (also called muting Replicas), Replicas never posts, reacts, or starts work, even when someone @mentions it. It still reads messages, including posts from apps like alerting tools, as the channel’s level allows and follows the channel’s instructions, so it can watch one channel and report somewhere else. For example, it can file a Linear ticket for each customer report and post it in #triage, or analyze each alert in #infra-alarms and post findings in #infra-team. Admins ask Replicas to turn on silent mode for a channel, or for every Slack Connect channel without its own setting:Hand off to a Manager
Ask @Replicas to send a thread to a Manager by name, such as@Replicas send this to App Support, or put it in a channel’s instructions, such as “send actionable messages to App Support”. The Manager gets the whole thread and replies in it. When you say “my App Support”, Replicas picks your own Manager with that name and asks only if you have more than one. If you have none, it offers the ones you can see and says whose each is.
How It Works
When you mention @Replicas in a channel:- Replicas adds an 👀 reaction to acknowledge your message
- If multiple environments are configured, Replicas resolves one for you and only posts a dropdown when it cannot, see Environment Selection
- A workspace is created for the task in that environment
- The agent sends a brief acknowledgment, then works on your request
- When done, the agent replies in the thread with results (and a PR link if code changes were made), with a View PR button on the reply that first shares the pull request
[↗︎] that opens the Replicas workspace without expanding a link preview.
Direct Messages
You can also DM the bot 1:1. 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.
A group DM that includes Replicas works like a channel: mention @Replicas to give it a task.
Manager channels
Give a Manager its own channel from the Slack button in its header: Create #manager-name makes a public channel and invites you, and Use existing channel links a channel Replicas is in. You can also ask the Manager to create or link one. In that channel, mentioning @Replicas messages the Manager instead of starting a new task, including in threads. The Manager replies under its own name and icon, and its ships post there as “ship name · Manager name” with the same icon. Messages without a mention go to the Manager too, which answers only the ones meant for it. A thread another workspace is working in stays with that workspace. A linked channel listens at Balanced or higher unless you give it its own level: at Low the Manager hears untagged messages only in its own threads or when they name it, and at Mentions only it hears only mentions. To change it, ask @Replicas in the channel, like@Replicas be more proactive here. The Manager changes it, and the same people can change it as anywhere else. New posts from other apps, such as PostHog or an alerting tool, go straight to the Manager, which handles each one in its own thread.
Only people who can see the Manager in Replicas reach it; anyone else who mentions @Replicas there gets a note only they can see. Apps’ replies in threads are ignored, and so are another company’s apps in a Slack Connect channel. Unlinking the channel stops this and leaves the channel in Slack. Archiving or deleting the Manager also stops it, and archives the channel if Replicas created it; a channel you linked with Use existing channel stays as it is. Slack doesn’t let apps unarchive channels, so a restored Manager shows its channel as archived, and you can create a new one from the same menu. Replicas can only create public channels.
Environment Selection
Workspaces are created inside an environment, and the env’s repositories are cloned. If your organization has multiple environments, Replicas works through the following in order and asks you to pick only when none of them can decide:- An inline
[env:name]tag in your message, matched against environment names (e.g.,@Replicas [env:backend] add a login page). - Your personal default, then your organization’s default.
- Automatic routing, which infers the environment from the message context (repo names, file paths, channel name) when confident.
- A dropdown in the thread, so you can select one yourself.
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. Routine follow-ups resume work without a separate acknowledgement. New tasks still receive one concise initial acknowledgement that identifies the concrete work starting without restating the full request. When several messages belong to the same ongoing task, Replicas treats them as one update instead of posting a status for each one. Follow-ups still receive text when they ask a direct question or need a meaningful status, outcome, or delivery-failure update. For new tasks, Replicas adds an eyes acknowledgement and starts Slack’s working indicator before slower triage or workspace startup. Slack’s working indicator remains visible while a queued or relayed follow-up is being processed. Follow-ups wake sleeping workspaces and keep using the linked workspace’s coding agent and model. An archived workspace is restored when it receives a follow-up. If a newer workspace attaches to that thread, future replies go to the newer workspace. The selection changes only when you change it in the workspace. Ask @Replicas to stop in the thread (“stop”, “cancel that”) to stop the workspace’s current turn, like its Stop button. Add “and close this” to also archive the workspace. Organization members and the person who started the work can stop it. You can attach or switch a thread’s workspace with the CLI Slack thread commands. If the workspace is deleted and you mention @Replicas again in that thread, a new workspace is automatically created.Fork a Thread
Open a message’s More actions menu inside an active Replicas task thread and select Fork task to start a separate task without interrupting the original agent. The form starts with the selected message as its instructions and the current channel as its destination. You can edit either before submitting. The fork inherits the source workspace’s environment and receives the full thread conversation and images as context. It starts as a top-level message in the selected channel, where both you and Replicas must be members.Merge from Slack
Once a GitHub pull request’s checks pass and it’s approved (or needs no approval), a merge button appears next to its View PR button, with other allowed methods in the ⋯ menu. It hides again if checks start over or fail. It merges with your own linked GitHub account under the same rules as the review page, so your Slack account must match your Replicas account. Bypassing branch rules and merge queues stay in the app. GitLab merge requests don’t get the button yet.Pull Request Notifications
When a PR or MR created from a Slack workspace is merged or closed on GitHub or GitLab, Replicas posts a notification to the originating thread. The notification includes the number, title, link, and the person who merged or closed it. A colored bar on the left of the message reflects the outcome at a glance: purple for merged requests and red for closed ones. If the Slack sender enables Open pull requests in Graphite, agents use Graphite links for GitHub PRs in follow-up responses, and merged or closed notifications use the workspace owner’s preference. GitLab merge request links are unchanged.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
- Images attached to messages in the thread
- Channel name
- User names of participants
Agent access
Workspace agents can download Slack attachments through the authenticated SDK:replicas.slack.call() for supported Slack methods, including file-upload reservation and completion.
Newly created workspaces instruct agents to keep routine Slack updates short and natural, post comparisons such as rankings or per-team numbers as a table, and consult Slack’s live Block Kit catalog before choosing display-only blocks or URL buttons. Existing workspace skill copies are not refreshed.
Workspaces created before the gateway retain compatibility with their existing tokens. Agents should use the SDK when available. Customer-defined tokens remain separate from the organization integration.
Post a Summary from the Composer
In a workspace’s chat composer (or the app prompt composer when creating a workspace), click the chevron on the Send button and choose Send & post to Slack, then pick a channel. The message sends as usual and the agent posts a single completion summary (including any pull request links) to that channel once it finishes the task. Slack must be connected for the option to appear, and it only lists channels the bot can access. Sending with the arrow button (or Enter) skips the Slack post.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