---
title: "Email your computer"
description: "Send a task to the inbox attached to a computer and read the reply."
canonical: "https://www.cool.computer/docs/use/email"
last_updated: "2026-11-20"
---
# Email your computer

> Send a task to the inbox attached to a computer and read the reply.

Every computer has an inbox at `name@mail.cool.computer`. The inbox stays with the computer until you delete it.

## Send a task

Write a direct instruction from the email address on your Cool Computers account:

```text
To: bakery@mail.cool.computer
Subject: Menu update

Add today's sourdough to the menu and publish it.
```

The agent inside the computer works in `/home/runtime` and replies to the thread with its result. Reply to the same thread when you want it to continue.

## Who can start a task

Only mail from your verified account address can start work, and only when it carries a DKIM signature from that address's own domain. Other messages reach the inbox but don't run a task. Each email's `intake_outcome` and `intake_detail`, in `cool email read` and the HTTP API, say why and what to do next.

### Turn on DKIM for your own domain

New Google Workspace and Microsoft 365 domains don't sign mail with their own domain until an admin turns it on: Google signs as `*.gappssmtp.com` and Microsoft as `*.onmicrosoft.com`. Your email then doesn't start a task (`rejected_owner_domain_unsigned`), and Cool Computers replies with these steps, at most once an hour per computer.

To check, send a test email to another mailbox and open the received copy's original headers (in Gmail, **More** → **Show original**). Its `Authentication-Results` must show `dkim=pass`, and the `d=` of the matching `DKIM-Signature` must be your own domain; `d=…gappssmtp.com` or `d=…onmicrosoft.com` means domain signing is off.

- **Google Workspace:** admin.google.com → **Apps** → **Google Workspace** → **Gmail** → **Authenticate email** → select your domain → **Generate new record** → add the TXT record it shows at `google._domainkey.<domain>` at your DNS provider → back in the console, click **Start authentication**. On a domain whose Gmail was turned on in the last 72 hours, **Generate new record** may not work yet; try again later. After **Start authentication**, signing can take up to 48 hours.
- **Microsoft 365:** security.microsoft.com → **Email & collaboration** → **Policies & rules** → **Threat policies** → **Email authentication settings** → **DKIM** → select your domain. If no keys exist yet, click **Create DKIM keys**. Add the two CNAME records it shows at your DNS provider, then turn on **Sign messages for this domain with DKIM signatures**.
- **Other providers:** turn on DKIM signing for your domain in your email provider's settings.

## Follow a task

Open [Chats](/app/chats) to follow the conversation started by your email. The reply also arrives in the original email thread. Reply to that thread to continue the task.

## Read and send mail with the CLI

```sh
cool email bakery
cool email read bakery <email-id>
cool email send bakery --to you@example.com --subject "Report" --text "Done."
cool email reply bakery <email-id> --text "Got it, thanks."
```

`cool email bakery` lists the newest mail, received and sent. `reply` answers one email in its thread. Every computer has an inbox, with or without a VM. Inside the computer, leave out its name: `cool email send --to you@example.com --subject "Report" --text "Done."`.

The HTTP API and the [MCP server](/docs/agents/other-mcp-clients#connect-it-yourself) also read and send mail. Obtain approval for the exact recipient and content before sending.
