Ask about production without leaving Slack. Polylane answers with the evidence.
Install it once, then set per-channel rules for when it speaks up and when it stays quiet.
Get started for free
# engineering 
checkout feels slow. is that us or payments-api?
Us. checkout-edge Wall Time P99 is 18× its own baseline
and the requests are queuing for a Hyperdrive connection, not on a downstream call.
payments-api is answering in 180ms, flat for a week.
Deploy 9f3c2a1 at 2:02 AM
shrank the hd-prod pool
from 50 connections to 5.
how long has it been queueing like that?
Nine minutes, since the deploy landed. It never went above 2 before that. I submitted a PR fix and tagged @justin to deploy 2 minutes ago.
Open in Polylane Configure
It already knows your stack.
-
Mention it anywhere
Mention @Polylane in any channel or DM. It answers in the thread, shows what it's doing as it works, and picks up where it left off when you reply.
-
It chimes in when it can help
It's on by default and deliberately shy: it only speaks up when it has something useful to add, and never too often. Turn it off with /polylane unwatch, or just ask it to stop.
-
Every channel gets house rules
Give each channel standing instructions, like answering as the team's on-call helper, keeping replies brief or linking the runbooks. Anyone in the channel can set them.
-
The fix reports back to the thread
Ask for a fix in Slack and updates come back to the same thread: failed CI, the merge, the close. Reply there to steer it.
-
What's open, without the scrollback
The app's home tab lists every open incident: waiting on a person, being worked by Polylane, or ruled out. Every row opens the investigation.
-
Notifications where the team lives
Connecting creates #polylane-notifications for new issues and the weekly digest, each with a link back to the evidence.
Only the alerts worth reading. Your monitors already page you. Polylane won't do it twice.
New issues, usage warnings and the weekly digest, each with a link back to the evidence. Only Polylane's own critical and high-severity detections notify, so nothing your monitors already sent shows up twice.
I just opened a PR to fix Critical latency degradation in checkout-edge worker
in coreplane/checkout-edge, could someone review?
It's here: coreplane/checkout-edge#142
Open in Polylane
These prompts already work. Copy one, swap your own service name in, and run it.
Give it to your coding agent and let it cook.
“We're seeing 500s on api.example.com. Start an investigation and post findings to #incidents.” “Summarise the open incident for the exec channel: impact, cause so far, next steps.” “What should support tell customers about yesterday's checkout errors? Keep it accurate.” Related guides
Common questions.
Is the Slack agent a different agent?
No, the same one, reading the same graph and the same telemetry. A thread in Slack is a thread in Polylane.
Will it talk in channels uninvited?
Only when it has something useful to add, and never too often. /polylane unwatch turns it off.
Can I give one channel its own rules?
Yes. Anyone in the channel can give it standing instructions, and it follows them there.
Can I ask for a fix from Slack?
Yes. Updates come back to the same thread: failed CI, the merge, the close. Reply there to steer it.