# Putting an agent in a shared thread makes it a colleague

DevFeed: [Putting an agent in a shared thread makes it a colleague](<https://devfeed.tech/articles/putting-an-agent-in-a-shared-thread-makes-it-a-colleague-15994.md>)

Original publisher: [Read original article](<https://workos.com/blog/agents-in-shared-threads-social-contract>)

Author: WorkOS

Published: 2026-08-27T15:16:58Z

Content type: opinion

Language: en

Sources: [WorkOS Blog](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Slack](<https://devfeed.tech/topics/slack.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [context](<https://devfeed.tech/tags/context.md>), [slack](<https://devfeed.tech/tags/slack.md>), [threads](<https://devfeed.tech/tags/threads.md>)

## AI overview

The article argues that placing AI agents in shared Slack threads makes them function like colleagues, creating social and operational questions around addressing, assignment, permissions, presence, and audience. Drawing on the experience of running more than 80 team agents, it presents mention-only responses and a distinction between room membership and assignment as practical rules.

## Source excerpt

Internal AI moved from dashboards into Slack threads. That changes addressing, mandate, presence, and audience -- questions that used to apply only to people.