How Armbrain handles outbound emails -- every draft is shown for your review before it goes out.
Why This Exists
Armbrain can draft and send emails on your behalf: follow-ups after meetings, client updates, nurture sequences, introductions. Sending an unreviewed message to a client is a risk no CMO should take.
By default, Armbrain shows you every outbound email before sending it. You see the full draft (recipient, subject line, and body). Nothing sends until you approve it.
How It Works
When Armbrain prepares an email (via /cmo-write or any workflow that involves sending), you see the complete draft:
To: alice@acme.com
Subject: Follow-up: Q2 campaign timeline
Hi Alice,
Following up on our call this morning...You then approve or edit:
- "Send it" / "Looks good" / "Approved" -- Armbrain sends the email as shown.
- "Change the subject to..." or "Make it more concise" -- Armbrain revises the draft and shows it again for approval.
- "Don't send" or "Cancel" -- Nothing is sent.
This applies to every outbound email, whether it is a one-off follow-up or part of a batch sequence. No exceptions by default.
Turning Off Approval
If you trust the AI drafts and want routine emails to go out automatically, you can turn off that approval gate. This global setting on your personal mind applies to all clients at once.
"Turn on auto-send emails"This sets email_auto_send to true in your personal mind's preferences. To turn approval back on (disable auto-send):
"Turn off auto-send emails"This is a global setting, not per-client. When auto-send is on, ordinary follow-up emails across all clients can skip the approval step. Briefing emails assembled by an AI always require a human approval click; this preference cannot bypass that security boundary. When auto-send is off (the default), all drafted emails require your approval before sending.
When to Use Auto-Send
| Scenario | Recommendation |
|---|---|
| High-stakes client emails (proposals, strategy updates) | Keep approval on (default) |
| Routine follow-ups and status updates across all clients | Consider auto-send |
| Nurture sequences you have already reviewed | Consider auto-send after reviewing the first few |
| Early in your Armbrain usage | Keep approval on until you trust the drafts |
Checking the Current Setting
Every time you switch to a client, the response includes _email_policy so you always know whether approval is active. If the policy says require_approval, every email draft is shown before sending. If it says auto_send, emails go out immediately.
You can also ask directly:
"Is auto-send on?"Key Details
- Default is always approval required. The setting starts as
falseand requires an explicit opt-in to turn on auto-send. - The setting lives in your personal mind. It is a global CMO preference, not per-client. One toggle controls email behavior across all clients.
- All email channels are covered. Whether sending via Gmail MCP, Google Workspace, or any future email integration, the approval gate applies.
- Batch sends are also gated. If a workflow generates five emails, each one is shown for approval (unless auto-send is on).
- AI-composed briefing emails always require approval. The auto-send preference never applies to them.
- To change the setting, switch to your personal mind and use
mind(preferences={"email_auto_send": true}). Or say "turn on auto-send emails".