An agent now knows when it's replying in a group
An agent replying in a shared Slack channel is now told other people can read its reply, instead of assuming every conversation is private.
Summary
When an agent replies inside a shared Slack channel rather than a one-to-one message, it's now told that other people can see what it writes — so it treats a group conversation differently from a private one.
What You Gain
An agent that didn't know who else could read its reply had no way to adjust its tone or the detail it shared for a wider audience. Now it's explicitly told whether a conversation is direct, shared with a group, or of a shape it can't confirm — and in that last, uncertain case, it's treated as potentially shared rather than assumed private, so it's never careless with something that might not be a one-to-one chat. This builds on talking to your agents directly from Slack.
How It Works
An agent now checks the shape of a Slack conversation before replying: a direct message, a shared channel, or a conversation it can't confirm the shape of. In that last case, it's treated as potentially shared rather than assumed private, so it never tells itself a reply is confidential when it might not be.
Where to Find It
No setup is needed — this applies automatically wherever an agent is connected to Slack.
See what else shipped this month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.