Integrations · Coming soon
Slack
Planned, not built. Escalations and digests reach you by email today. Here is what a Slack channel would add.
The escalation should land where the team already is
The agent escalates rather than acting whenever it hits security, licence or hostile-tone signals, and it sends a weekly digest of what it handled. Both go out by email today. A Slack integration would route the same notifications to a channel of your choosing, with the audit link attached, so the thread starts where your team already talks. It is on the roadmap; it is not something you can enable now, and we would rather say that than let a logo imply otherwise.
Escalations, not chatter
Only the classes that stop the loop would post: security, licence, hostile threads, human-merge lanes. Not every action.
The weekly digest
What was triaged, handed off, merged and shipped, in one message, with a link into the audit log for each line.
Available today instead
Email notifications are live now, and outbound webhooks let you post into Slack with an incoming webhook of your own.
Next step
See what actually escalates
The escalation classes are documented, not improvised. Start there before deciding which channel should receive them.
Read the escalations doc
Ship more. Maintain less.
We expect software to be written faster than any team can review it. Bring your repos, your boxes and your keys. We bring the org that keeps up.