Guides
Guides for teams that work in chat.
Long-form, practical write-ups on MCP, terminal clients, diagrams, bots, shortcuts and incident response. Each one stands on its own, whatever chat app you use.
- How to give an AI agent access to your team chat with MCPHalf of what an agent needs to know about your project is in chat: decisions, incidents, who owns what. Here are the ways to connect an MCP client to team chat in 2026, what each costs in setup, permissions and risk, and how code mode changes the picture.→
- Build a chat bot with a single HTTP endpointA chat bot doesn't need a socket connection, a framework or a server that stays up. This guide builds one as a single URL: verify the signature, answer the event, call the API back. Real code, with and without an SDK.→
- How to run incident threads in chatIncidents happen in chat whether you plan for it or not. A playbook that keeps the channel readable at 3 a.m.: severity levels, roles, one channel per incident, thread discipline, copy-paste templates, and a postmortem that writes itself from the log.→
- Keyboard-first team chat: a shortcuts cheat sheet (Slack vs Discord vs Hasarak)The shortcuts that matter for getting through chat without the mouse, side by side. Slack and Discord keys are checked against their official help pages, and the places those pages disagree with themselves are marked.→
- Mermaid diagrams in team docs: a practical guideDiagrams-as-code that live next to the text, review like code and never go stale in a drawing tool. Five copy-paste examples, where Mermaid renders, and the mistakes that break a diagram.→
- Terminal chat clients in 2026: every option comparedWhich chat clients actually work in a terminal today, which ones are maintained, and what each one costs you in setup and risk. Covering Slack, Matrix, IRC, Discord, Zulip, Mattermost and Hasarak, with repository links and release dates checked in October 2026.→