Agents Belong Where the Thinking Already Happens
Slack channel integration maps to the joelclaw gateway pattern: put the agent inside the existing work channel instead of inventing another inbox.
The source is a private Slack service page for a JoelClaw integration, backfilled from a Joel-authored #brain-joel message. The available record is tiny: an integration named JoelClaw was added to that channel.
That’s still enough to remember the shape. An agent doesn’t need a sacred new dashboard if the work already lives in Slack. Drop the integration into the channel where the thinking happens, let messages become events, and route the useful bits into the system.
The useful pattern for joelclaw is the same one behind the gateway: channels are inputs, not destinations. Slack apps, webhooks, and channel events can be boring plumbing that gives agents context without asking humans to change where they work. Boring plumbing is underrated as fuck.
Key Ideas
- A Slack integration can turn a normal team channel into an agent input surface without requiring a separate UI.
- The interesting artifact is not the private service page; it’s the act of adding JoelClaw to
#brain-joel, a channel where context was already accumulating. - This matches the joelclaw gateway model: normalize messages from many channels into one event-driven system.
- Private SaaS configuration pages should still leave public breadcrumbs when they reveal a reusable pattern.