For engineering teams
Incidents, runbooks and your agents in one place.
Work an incident in a thread, write the postmortem as a page next to it, and let Claude Code, Cursor or your CI scripts read and post in the same workspace.
Threads that keep incidents readable
Each problem gets its own thread, and the inbox brings back only the replies and mentions that involve you.
Runbooks and postmortems as pages
Tables, timelines, images and Mermaid diagrams, edited together and one click from the incident channel.
Your agents, plugged in
Add the workspace's MCP URL to Claude Code or Cursor and it can read the thread and post a summary as you.
Your scripts, too
CI and deploy tooling can post through the MCP server, or as a connector: one HTTP endpoint.
For the playbook, read How to run incident threads in chat, and for wiring your own tools in, Build a chat bot with a single HTTP endpoint.
Related
- Keep maintainers on the same page.Chat for maintainer teams: threads for reviews and releases, pages for contributor guides and release checklists, an MCP server for your scripts, and a free plan.→
- Async by default, for teams across time zones.Remote and async-friendly team chat with threads, one inbox for mentions and replies, snooze, and docs edited together. In the browser, nothing to install.→
- Chat and docs in one tool, from day one.One workspace for chat, docs and your AI tools. A free plan for small teams and one paid Team plan as you grow. No add-ons.→
- IntegrationsCursor, ChatGPT, GitHub, Linear, MCP and custom connectors.→