Community Conversation
How Watchers participate in ordinary community chat, not just react to commands.
Where configured, a Watcher can participate naturally in ordinary conversation — greetings, casual chat, community questions, project discussions, and follow-ups that build on earlier context.
A Watcher isn't meant to reply to every message. It decides whether responding actually adds value based on its configured role, what's already happened in the conversation, and how directly it's being addressed — silence is frequently the correct outcome, not a bug.
A Watcher generally responds when it's directly addressed (mentioned, replied to, or called by name), and more selectively to ambient/general conversation, weighing recent activity so it doesn't repeat something another Watcher or a human just said.
Multiple Watchers in the same Community coordinate so they don't all reply to the same message at once — see "Multi-Watcher Communities" for how that works today.
Fine-grained response controls (e.g. a dashboard toggle for "only respond when mentioned" or a fixed reply frequency) are not currently exposed as customer-facing settings — response behavior is decided automatically per message rather than configured as a fixed rule. This is a planned area, not something available to configure today.