Code review for the emails your agents write.

Letting an agent send email unchecked is a liability. Reading every single draft yourself doesn’t scale. With comail, your writing agent can only create drafts, while a separate reviewer agent checks each draft against your policies and either sends that exact version or kicks it back with feedback.

Takes a minute to apply. No credit card required.

Draft r-5512review history

Re: Charged twice for March

sentsupport-agent → dana@brightloop.io

  1. support-agent requested a review version 1
  2. review-agent returned the draft

    Promises the $480 refund by Friday. Per refund-policy.md, refunds take 5–7 business days—don’t commit to a specific day.

  3. support-agent revised the draft and re-requested review version 2
  4. review-agent approved version 2 · sent by comail
One draft, two rounds. The reviewer cannot edit the draft—it either approves and sends the exact version it read, or returns it with comments.

The problem

Every email an agent sends is a deploy you can’t roll back.

Once an email leaves your outbox, you can’t recall it. Most teams get stuck choosing between letting an agent send unchecked and reading every draft by hand. Engineering teams solved the same trade-off decades ago: nobody pushes straight to main.

01

Unchecked sending is a liability

One hallucinated discount, one invented SLA promise, or one prompt injection hidden in an incoming thread, and an unreviewed reply is sitting in a customer’s inbox with your name on it.

02

Manual review makes you the bottleneck

Keeping an agent in drafts-only mode is safe, but when it handles dozens of routine billing or support threads a day, you spend your afternoon clicking Send in Gmail.

03

An isolated reviewer catches what the writer misses

A second agent with a clean context window—focused strictly on your policies and insulated from the customer’s raw thread—can approve routine replies automatically and reject anything that crosses a line.

How it works

Open a review, request changes, approve and send.

  1. Split drafting and sending across two agents

    Create support-agent with access to your support threads and send set to drafts only. Create review-agent with zero thread labels of its own, and grant it permission to review and send support-agent’s drafts—either to anyone or only to approved addresses and domains.

  2. The writer drafts a reply and requests review

    support-agent calls create_draft with request_review: true. comail notifies eligible reviewers and labels the message being answered with co:support-agent/review-requested in Gmail so you can see a review is underway.

  3. The reviewer approves or returns the draft

    review-agent calls list_reviews to inspect the exact recipients, subject, body, and attachment list. It either sends that version with approve_draft, or kicks it back with return_draft and feedback that only the writer can read.

  4. The writer revises and resubmits

    When a draft is returned, support-agent receives a notification, reads the reviewer’s feedback, updates the draft with update_draft, and requests a fresh review on version 2.

support-agent — claude

> Draft replies to threads labeled co:support-agent and submit every draft for review.

comail · get_thread (thread_id: "thr_6c21e0")

From: Dana Ortiz <dana@brightloop.io>

Subject: Charged twice for March

comail · create_draft (thread_id: "thr_6c21e0", request_review: true)

review: {status: "requested", reviewers: ["review-agent"]}

notification review r-5512 · mine · returned

comail · list_reviews (role: "mine")

returned by review-agent: “Promises the $480 refund by Friday. Per refund-policy.md, refunds take 5–7 business days—don’t commit to a specific day.”

Updating the refund timeline to 5–7 business days and resubmitting.

comail · update_draft (draft_id: "r-5512", body: "…", request_review: true)

review: {status: "requested", reviewers: ["review-agent"]}

The writing agent reads support threads and creates drafts, but has no permission to send email directly.
review-agent — claude

> Check support-agent’s drafts against refund-policy.md. Approve compliant replies; return anything that overpromises.

notification review r-5512 · to_review · pending

comail · list_reviews

support-agent → dana@brightloop.io · version 1

“…you’ll have the $480 back in your account by this Friday.”

Promises a specific date instead of the 5–7 business day window. Returning.

comail · return_draft (draft_id: "r-5512", version: "1", reason: "Promises the $480 refund by Friday…")

status: "returned"

notification review r-5512 · to_review · pending

comail · list_reviews

support-agent → dana@brightloop.io · version 2

“…refunds take 5–7 business days to appear on your statement.”

comail · approve_draft (draft_id: "r-5512", version: "2", idempotency_key: "c41f…")

status: "sent"

The reviewer has zero Gmail labels of its own. It never sees the inbox—only the drafts submitted for review.

Mental model

If you’ve used pull requests, you already know the workflow.

In code reviewIn comail
Branch protection (no direct push)New agents default to drafts only. The writing agent has no permission to send mail on its own.
Open a pull requestcreate_draft with request_review: true
CODEOWNERSPer-reviewer settings define which agents’ drafts the reviewer can approve, and which recipients or domains it may send to.
Request changesreturn_draft with feedback, stored encrypted and visible only to the writing agent.
Push a fix and re-request reviewupdate_draft with the revised body and request_review: true
Approve and merge a specific commitapprove_draft requires the exact version ID the reviewer read and sends it unchanged. The reviewer cannot edit the draft.
New commits dismiss stale approvalsAny change to the draft—by the writing agent or by you in Gmail—increments the version and cancels pending reviews.
Status checks on the PRLabels on the message being replied to: co:support-agent/review-requested while pending, co:review-agent/review-returned when returned.
Scheduled mergeapprove_draft with send_at. The approved draft waits in your send queue, and both agents’ permissions are re-checked when it’s due.
Maintainer overrideThe dashboard’s send queue shows every draft awaiting review so you can cancel any of them, and drafts no agent is allowed to send stay in Gmail Drafts for you.

Guardrails

Why a second agent is harder to fool than the first.

01

Version-locked approvals

A reviewer can never edit a draft on the way out. approve_draft requires the exact version ID the reviewer read; if the writer revises the draft or you edit it in Gmail, the version changes and stale approvals are rejected.

02

No inbox access for the reviewer

Give review-agent zero thread labels and list_reviews is all it can see: pending drafts, never the underlying Gmail threads. That cuts off direct access to customer mail, but the draft body is whatever the writer put in it — if the writer copied customer text into a draft, the reviewer reads that text too, and should treat it as untrusted input.

03

Re-verified at the moment of sending

Right before Gmail sends (including when a scheduled send_at timestamp arrives), comail verifies again that the writer still has label access to the thread and the reviewer is permitted to email those recipients.

Permissions

Neither agent can send an email on its own.

The writer can read customer threads and compose drafts, but can’t send. The reviewer can approve and send the writer’s drafts, but can’t read your inbox or send mail of its own.

Writes replies

support-agent

Reads threads labeled co:support-agent, writes replies as drafts, and requests review from review-agent. It cannot send mail directly.

view allow co:support-agent
view deny default
attachments allow —
send deny drafts only

Reviews and sends

review-agent

Has no thread labels of its own, so it can’t read your inbox. It only sees drafts submitted by support-agent and can approve and send them unchanged.

view deny default, no label
review allow support-agent’s drafts
review allow to anyone
send deny its own mail

FAQ

Common questions.

Can I review drafts myself instead of using a second agent?

Yes—that’s how every new agent works by default. When no reviewer agent is configured (or when a draft is addressed to someone the reviewer isn’t permitted to email), the draft simply sits in Gmail Drafts until you review and send it yourself.

What happens if I edit an agent’s draft in Gmail?

You take ownership of it. As soon as you edit a draft in Gmail, comail cancels any pending agent review and locks the writing agent out of modifying it further.

How do I see which threads are waiting for review?

In Gmail, the message being replied to carries co:support-agent/review-requested while waiting for review and co:review-agent/review-returned if sent back. In the comail dashboard, the send queue lists every pending and returned draft along with the reviewer’s status.

Can the reviewer schedule a send for later?

Yes. approve_draft accepts an optional send_at timestamp. The approved draft waits in your send queue (where you can cancel it anytime) and only goes out if both the writer and reviewer still have permission when the scheduled time arrives. Pausing either agent holds the send.

Can multiple reviewer agents cover the same writer?

Yes. If you authorize more than one reviewer for a writing agent, comail tells the writer which reviewers are eligible for each draft. The first reviewer to call approve_draft or return_draft resolves the review.

Request access

We’re onboarding beta users in small batches. Tell us what you want your agent to handle; specific use cases go to the front of the line.

Clients / harnesses (optional)

Select all that apply.

We’ll only email you about the beta. No card, no newsletter.