File every expense without sharing your inbox.

Your receipts land in the same inbox as payroll, board decks, and legal threads. Instead of giving an accounting bot full Gmail access just to grab a dozen PDFs a month, give it a single label: co:bookkeeping-agent. Label an invoice once, let your agent book the expense, and let a separate admin agent turn that sender into a rule for next month.

Takes a minute to apply. No credit card required.

Label a receipt co:bookkeeping-agent in Gmail and only that agent can read it. It gets notified, reads the invoice, and books the expense.

How it works

Label the first invoice from a vendor. Never touch the next one.

Recurring expenses come from the same billing addresses every month. Once you label the first receipt from a new vendor, comail’s rules handle every invoice after that.

  1. Create a dedicated bookkeeping agent

    Create an agent named bookkeeping-agent in comail. That adds a hidden co:bookkeeping-agent label to your Gmail account and gives you a dedicated MCP endpoint. Connect Claude, ChatGPT, or your own script to that URL alongside your accounting tool.

  2. Label an invoice in Gmail

    When a receipt arrives from a new tool you signed up for, apply co:bookkeeping-agent in Gmail on your laptop or phone. Only that thread becomes visible to the agent—the payroll run, investor update, and personal emails sitting right next to it stay completely out of reach.

  3. Your agent pulls the PDF and books it

    Applying the label triggers a live notification over HTTP. Your agent wakes up, fetches the message and attached invoice via get_message and get_attachment, and logs the entry in your accounting software. It can’t send email, search outside its label, or widen its own permissions.

  4. An admin agent adds a rule for next month optional

    On a daily schedule, a separate management agent checks which senders you’ve labeled co:bookkeeping-agent. When it spots a new billing address, it adds a comail sharing rule for that sender so future invoices get labeled automatically on arrival.

Zero-maintenance routing

Auto-learn new vendors without exposing a single invoice.

The annoying part of an allow-list is keeping it updated whenever you start paying for a new service. Instead of opening a dashboard every time a new receipt hits your inbox, you can delegate rule creation to a separate admin agent connected to comail’s management MCP.

You control what a management agent can inspect down to the field. For this job, it only needs permission to read labels and email addresses—not subject lines, message bodies, or attachments. It can see that you labeled an email from billing@figma.com, and nothing else.

Because the rule matches the exact billing address (or a dedicated alias like invoices@yourco.com), future invoices are labeled automatically while product updates and marketing emails from the same vendor stay private. You also choose whether a new rule backfills existing threads or only applies to new mail.

admin-agent — claude — daily check

> Check co:bookkeeping-agent for new vendors and add sharing rules for their billing addresses.

comail-admin · list_labels

co:bookkeeping-agent · Label_8213

comail-admin · list_messages (label_id: "Label_8213")

From: Anthropic, PBC <invoice+statements@mail.anthropic.com>

From: Figma <billing@figma.com>

Subjects, bodies, attachments: hidden by management permissions

comail-admin · get_agent_access (agent_id: 4)

only_addresses: ["invoice+statements@mail.anthropic.com"]

billing@figma.com isn’t in the rules yet. Adding it for future mail.

comail-admin · set_agent_access (agent_id: 4, only_addresses: ["invoice+statements@mail.anthropic.com", "billing@figma.com"], apply_to: "new_only")

ok · future mail from billing@figma.com will get co:bookkeeping-agent

The admin agent sees which sender addresses carry the label, never what’s inside the emails. Every rule it adds appears in your comail dashboard.

Separation of duties

Why split reading and routing across two agents?

An agent that can read your mail, run accounting tools, and edit its own access rules is one prompt injection away from reading your whole inbox. Splitting the roles keeps both agents locked down.

Reads invoices

bookkeeping-agent

Connected to its own mail MCP endpoint. It reads threads labeled co:bookkeeping-agent, downloads attached PDFs, and logs expenses. It cannot send mail or change which threads it sees.

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

Manages rules

admin-agent

Connected to the management MCP endpoint with only two of the five read permissions enabled: labels and addresses. It updates routing rules, can never send mail, and can be time-boxed or paused anytime.

labels allow read
addresses allow read
subjects deny —
content deny message bodies
attachments deny —
send never —
01

Prompt injections hit a dead end

Invoices arrive from outside your company, which makes every PDF untrusted input. Even if a malicious invoice tries to hijack your bookkeeping agent, that agent can’t search the rest of your inbox, send email, or widen its own access.

02

The agent that writes rules is blind to content

Your admin agent only sees label IDs and sender addresses. Even if you leave management access open for a daily cron job, it never sees a subject line, dollar amount, or attached PDF.

03

Instant audit and revocation in Gmail

Search label:"co:bookkeeping-agent" in Gmail on desktop or mobile to see every thread the agent can read. Remove the label from any thread and access is gone on its very next request.

FAQ

Common questions.

Does the management agent need standing access?

Only if you want it to run on a schedule by itself. By default, management access opens for a 60-minute setup window and then turns itself off. If you run a daily check, you can leave management access enabled and pause or revoke it from the dashboard whenever you like.

Can a rule share threads I didn’t mean to share?

A rule only ever applies co:bookkeeping-agent, and every rule is visible and editable in your dashboard. Rules never re-apply a label you removed manually, and when the agent’s blocking label is turned on, no:bookkeeping-agent always overrides co:bookkeeping-agent.

What if a vendor sends invoices and marketing emails from the same address?

An address rule would match both. For those senders, enable the management agent’s Filters permission so it can create a standard Gmail filter matching both the sender address and words like “invoice” or “receipt”. Gmail filters apply to new mail as it arrives.

Can one bookkeeping agent watch multiple inboxes?

Yes. You can attach your personal work inbox, a shared billing@yourco.com address, and a personal Gmail account to the same agent. It uses a single MCP URL across all of them, with separate labels and rules per inbox.

Which accounting tools does comail integrate with?

comail handles the Gmail side over MCP. Your agent books expenses using whatever accounting MCP server, API, spreadsheet, or local script you pair it with in your client.

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.