# Polylane in Slack: mention it to investigate production

> Published 2026-07-24 · Updated 2026-11-18 · Canonical: https://polylane.com/changelog/2026-07-24-polylane-in-slack/

Mention Polylane in Slack to ask about production: it streams its reply, shows progress on long turns and reports pull request updates back to the thread.

## What changed

Mention Polylane in Slack and it reacts straight away, shows that it's thinking and streams its reply as it writes. It appears in Slack's Agents tab with suggested prompts.

### Live progress

Long turns post one status message and update it as each step completes. If a turn fails, Polylane says what happened and how to resume.

### Joins conversations it can help with

In channels it belongs to, Polylane replies to messages it can help with even when nobody mentions it. Set a channel to mention-only to turn this off.

### Pull requests report back to the thread

When a fix starts from a Slack thread, the thread gets the pull request link, CI failures and their fixes, review replies, and a reaction when it merges.

## Duplicate issues share one investigation

Every new issue is checked against the open ones in your workspace. A confirmed duplicate is linked to the original and shares its investigation. Log lines are grouped by their shape, so an unfamiliar ID format no longer opens a new issue or reopens an old one.

## Why it matters

Production questions start in Slack, where the team already talks about errors and deploys. Answering in the thread saves the switch to another tool, and keeps the investigation and its pull request where everyone following the problem can see them.

## How to use it

1. Connect Slack from the Slack integration page in the console and approve the install.
2. Invite Polylane to your incident, alerts and on-call channels with `/invite @Polylane`.
3. Mention it in a channel or send it a direct message, for example "did we deploy checkout today?". Replies in the Slack thread continue the same Polylane thread, which also shows under **Threads** in the console.
4. Run `/polylane unwatch` in a channel to make it mention-only, and `/polylane watch` to turn replies without a mention back on.

## Related

- [Polylane in Slack](https://polylane.com/product/slack/)
- [Slack integration](https://polylane.com/integrations/slack/)
- [Investigations](https://polylane.com/product/investigations/)

## Improvements

- Pull requests: Production impact verdicts post as a comment on the pull request, and Polylane replies when you comment on it
- Pull requests: A changed verdict posts a fresh comment so GitHub notifies you, and a push that could not be reviewed is marked on the comment
- Pull requests: Reviews check for deploy hazards: a rename and drop that old instances still read, a `CREATE INDEX` that blocks writes on a busy table, or an environment variable nothing provides
- Pull requests: Anyone who can see the pull request can open the investigation behind a verdict, read-only, from the comment
- Context graph: People and teams join the context graph from `CODEOWNERS`, deploy authors and owner tags, linked to what they own
- Context graph: Hold a resource in the topology to trace its blast radius, and drag resources to rearrange it
- Monitoring: Polylane writes checks for individual resources as well as accounts and integrations
- Notifications: A weekly digest emails every member a summary of issues, pull request reviews, fixes and changes
- Onboarding: Onboarding has a step to set up Polylane in your coding agent
- Console: The fixes list has search, and its filters, sort and page are kept in the URL

## Fixes

- Notifications: Notification emails reach the right recipients
- Console: Email domain auto-join works for password sign-ups, and accepting an invite no longer shows a 404
- Notifications: Removing a cloud account sends one email, and removing an integration sends one too
- Notifications: No fix email is sent when an investigation finds nothing to fix
- Pull requests: Polylane's own pull requests get a production impact review
- Context graph: The infrastructure graph is a top-to-bottom hierarchy again and opens at a readable zoom
- Console: Editing a row updates it in place without reloading the table
- Threads: Threads show their names in place of the agent's name

[All updates](https://polylane.com/changelog/)
