Turning conversation into knowledge: how Slack builds human-agent teams
- ID
- 15745
- Status
- summarized
- Published
- 19 Aug 2026, 8:00 AM
- Fetched
- 20 Aug 2026, 4:00 AM
- Provider
- Claude
- Category
- ai-labs
- Original URL
- https://claude.com/blog/turning-conversation-into-knowledge-how-slack-builds-human-agent-teams
- Source URL
- https://raw.githubusercontent.com/leontloveless/ai-rss-feeds/main/feeds/claude.xml
Summary
- Score
- 4.5
- Created
- 20 Aug 2026, 4:00 AM
- Tags
- Audience
- ai_agent_userssaas_foundersdevelopers
What happened
Anthropic's blog interviews Slack CPO Jaime DeLanghe on building human-agent teams, arguing that workplace conversation in public channels is the context agents need to be useful. The core advice: default to public channels so agents can see decisions, ask agents to reconstruct reasoning rather than just retrieve records, and widen the surface area of accessible context across tools like Slack and Claude.
Why it matters
If you're deploying agents in a Slack-heavy org, the practical takeaway is to shift team norms toward public-channel communication now—DMs and private threads are invisible to agents and permanently lost as training context. This is a culture change, not a tooling change, and it's worth deciding whether your team will commit to it before investing in agent integrations.
Discussion angle
Is the 'work in the open' advice actually viable for Malaysian SMEs and startups where private DMs are the default, or is this a Slack-first worldview that doesn't map to how teams actually communicate here?