Email Capabilities for ChatDev Agent Teams

Give ChatDev's collaborative agents the ability to send, read, and manage real email — with oversight controls that keep automated communications safe.


ChatDev simulates a virtual software company where LLM agents collaborate through natural language, taking on roles like CEO, CTO, programmer, and tester. When these agents need to communicate externally — sending project updates, client reports, or support responses — MultiMail provides the email infrastructure with safety controls.

MultiMail's oversight modes complement ChatDev's collaborative approach. In gated_send mode, any email drafted by a ChatDev agent is queued for human review before delivery. This means your agent team can autonomously decide when and what to email, but a human always approves the final message.

Integration works by adding email capabilities to ChatDev's phase system. Define custom phases that include MultiMail API calls for sending, reading, and replying to email.

Built for ChatDev developers

Safe External Communications

ChatDev agents communicate freely internally through chat chains. When those communications need to extend to real email recipients, MultiMail's oversight ensures a human reviews every outbound message.

Phase-Based Email Workflows

ChatDev organizes work into phases. MultiMail integrates naturally — an inbox check phase feeds context to a drafting phase, which creates emails queued in the approval phase before delivery.

Role-Specific Email Access

Not every ChatDev role should send email. Assign email tools only to appropriate roles (like a communications agent) while other roles focus on their specialties without email access.

Collaborative Email Drafting

Multiple ChatDev agents can contribute to an email draft through their chat chain process. MultiMail's API receives the final collaborative output for delivery after human approval.


Try it with your agent

No code, no dashboard. Paste this to your AI agent — it connects MultiMail, creates an inbox, and builds the flow for you.

1. Get MultiMail ready first: read https://multimail.dev/llms.txt, connect the MultiMail MCP server exactly as documented there, create a free inbox for this ChatDev workflow, and set up a verified sending domain before enabling any outbound email. 2. Wire MultiMail into ChatDev using ChatDev’s real extension surface: add custom Python tools in ChatDev’s functions directory and attach them to the relevant workflow nodes in the ChatDev workflow canvas or YAML workflow, so ChatDev agents call the connected MultiMail MCP tools instead of any hand-written email API. 3. Expose only three agent capabilities in the workflow: check the MultiMail inbox for new messages, draft a reply from the selected message and task context, and send or schedule an email through MultiMail. Do not add any unverified webhook, endpoint, delivery provider, storage layer, or custom mail transport. 4. Send one test email from the verified sender to my own test address. The ChatDev agent should check the inbox, draft a short reply, show the exact recipient, subject, body, and send or schedule action it intends to use, then wait for review. 5. Run the MultiMail connection in gated_send oversight mode for this ChatDev workflow, so every outbound email or scheduled email requires my explicit approval before MultiMail sends it. Mention monitored and autonomous only as later options, not as the default for this setup.

Step by step

1

Create a MultiMail Account and API Key

Sign up at multimail.dev, create a mailbox, and generate an API key from your dashboard. Your key will start with mm_live_.

2

Install Dependencies

Install ChatDev and the HTTP library for calling the MultiMail API.

3

Define Email Functions

Create Python functions that wrap MultiMail API endpoints for send, read, reply, and inbox operations.

4

Add Email Phases to ChatDev

Configure ChatDev phases that include email operations. Assign email capabilities to the appropriate agent role, such as a communications manager.

5

Approve Pending Emails

Review and approve pending emails in the MultiMail dashboard before they are delivered. All emails from gated_send mode appear here.


Common questions

Which ChatDev role should handle email?
Create a dedicated communications role or assign email capabilities to the CEO role, since it handles external-facing decisions. Avoid giving every role email access, as this can lead to duplicate or contradictory outbound messages from different agents in the chain.
Can ChatDev agents collaborate on drafting an email?
Yes. ChatDev's chat chain system lets multiple agents contribute to a message. One agent drafts, another reviews the tone, and a third handles the actual send through MultiMail. The gated_send mode adds a final human review layer before delivery.
How does oversight work with ChatDev's autonomous phases?
MultiMail enforces oversight at the API level regardless of how ChatDev structures its phases. Even if a phase runs autonomously without human involvement, any email sent through the MultiMail API in gated_send mode will be queued for approval before delivery.
Can I test email integration without sending real messages?
Yes. Use MultiMail's gated_send mode during development. All emails are queued for review rather than delivered, so you can inspect the output of your ChatDev email phases without any messages reaching real recipients.

Explore more

The only agent email with a verifiable sender

Email infrastructure built for AI agents. Verifiable identity, graduated oversight, and a hosted MCP server. Formally verified in Lean 4.