What does the job own?
This directory marks Inbox Manager as From xAI via the use-case gallery. The docs.x.ai use-cases page we fetched on 24 August 2026 walked eight worked examples and did not use that heading. The recipe still exists, and it still stops at draft. Chief of Staff reads mail among other channels. This Bot stays with the queue.
That distinction matters. A chief of staff drops mail that does not map to priorities. An inbox Bot stays with the queue. Pick the one you actually want to read in the morning.
Where does it stop?
Never send is the line. Gmail on these recipes is draft. The shared computer will keep the mailbox session for every other Bot on the account. If that is too much access, do not connect Gmail. See Grok Bot security.
Questions people ask
Is Inbox Manager an xAI use case?
The recipe file marks it From xAI via the gallery. The docs.x.ai use-cases page we read the same day did not use that heading. We keep the chip the file already has, and we keep the stop line: never send, never delete.
Can it archive or unsubscribe?
Not on the stock suggest lines. Those are changes. Keep them behind a yes until you trust the drafts.
Should I use this and Chief of Staff together?
You can. They will both see Gmail, because connectors are account-wide. Give them different stop lines or you will get two drafts of the same thread.
Related: Inbox Manager installer, Chief of Staff, Connectors.
Verified on 2026-08-24 against docs.x.ai/grok-bot/use-cases, docs.x.ai/grok-bot/approvals-security-and-privacy. Recheck the live pages before you change a plan or a vendor.
