Every's 3 rules for running one Slack agent for the whole company
every · x · 2026-10-30
Every launched a single Slack agent shared by the whole company. Engineer @bigwilliestyle shares 3 design rules: (1) Conversations — a shared agent must follow multi-party Slack threads, solved with a translation layer that organizes messages for the model and routes replies back to the thread; (2) Connections — keep tasks running when tool logins change, since every integration depends on someone's credentials; (3) truncated in source. Key lesson: shared company agents need very different design from personal ones.
More from coding & agent
- Anthropic launches Claude Duet, a proactive agent powered by Opus 5.5 — joellewenstein · 2026-10-30
- Spring AI 2.1 adds VectorStore.upsert for apps that bring their own embeddings — therealdanvega · 2026-10-30
- Auditing an LLM-built knowledge graph: 0 of 186 facts matched verbatim, 1/3 of edges hit wrong entities — JeremyCMorgan · 2026-10-30
- Same agent harness, opposite rankings: TB4 benchmark drama exposes eval chaos — lunwang1996 · 2026-10-30
- The eternal eval debugging meme: ask the vendor if it's data or harness, it's data — dejavucoder · 2026-10-30
- DropCut: Open-Source ComfyUI Rebuild of Higgsfield Turns Photos + Song Into Beat-Synced Reels — Mediocre-Purchase-62 · 2026-10-30