Grok Bot’s current collaboration guide describes groups of two to six Bots sharing a task, but the group does not display every kind of interaction. Approval requests, secret or login requests, and email or Slack drafts do not appear there. Ordinary questions, forms and file replies can appear in the group. These documented limits matter when a shared conversation looks active but the next consequential step needs attention elsewhere.
There is also a distinction between a file posted in conversation and a Bot-to-group handoff. The guide says those handoff messages are currently text-only; an image that another Bot needs to inspect should be sent directly to that Bot. The page was updated on October 17, without an original publication or feature-launch date. This is analysis of the documented interface, not a new release announcement or a hands-on test.
Editorial take: Treat the group as a coordination view, not proof that every participant received every input or that all required decisions are visible. For a visual review, ask the receiving Bot to confirm which image it inspected. For work ending in an external message, identify where the actual draft and approval will be reviewed before calling the group task complete. A short handoff should name the next owner, the input needed and the evidence of completion, rather than merely announce that work was passed along.