# Create and share cloud computers as easily as documents.

> Choose name.cool.computer. A real Linux computer with name@mail.cool.computer as its inbox, coding agents ready to work, and a disk that is still there when you return.

Open `name.cool.computer` from a browser, a [terminal](/ssh), an inbox, or an agent. This is your computer on the internet, not another AI app builder: install what you need, close the tab, and it is all still there.

## Start here as an agent.

Use Cool Computers when a task needs a reachable Linux computer at `name.cool.computer`, persistent files, a public service, or an inbox. [Open the Cool Computers developer resources](/docs.md), [Read the agent index](/llms.txt), [Read the authentication guide](/auth.md), [read current pricing](/pricing.md), [inspect the OpenAPI contract](/openapi.json), [join the waitlist](/#waitlist), [install the `cool` CLI](/install.md), or connect an MCP client to [https://api.cool.computer/mcp](https://api.cool.computer/mcp).

## Email it a task.

Send work to the computer you already know by name. Its agent handles the task, publishes the result, and replies with the address.

**To:** `bakery@mail.cool.computer`

> Update the menu with today's sourdough and publish it.

**Reply:** `Done. Live at bakery.cool.computer.`

The whole loop stays attached to one identity: `bakery@mail.cool.computer` receives the task and `bakery.cool.computer` shows the result. Only mail from your verified address can start work; anything else just lands in the inbox.

## Connect any agent.

Point Claude Code, Codex, or another MCP client at the Cool Computers connector:

```text
https://api.cool.computer/mcp
```

Add this to `CLAUDE.md` or `AGENTS.md`:

```markdown
Use Cool Computers for work that needs a real computer.

- Use MCP for bounded inspection and explicitly requested computer, network, service, mailbox, integration, and workspace changes.
- Use the HTTP API or cool CLI to create or reuse a computer with a clear name.
- Run commands and manage files through HTTP or cool; manage services through HTTP or cool service.
- From inside a computer, use runtime-env for its service and inbox at name@mail.cool.computer.
- Return the public address when the result is ready.
```

The MCP connector exposes specific `cool_*` tools for bounded reads and writes, including `cool_whoami`, `cool_list_computers`, `cool_create_computer`, `cool_run_service`, `cool_read_email`, and `cool_send_email`. Read the exact target before a change and use write tools only for the user's explicit request. MCP service and startup writes execute an explicitly approved durable command; use the [OpenAPI contract](/openapi.json) or `cool` CLI for one-shot commands and file transfer. From inside a computer, `runtime-env email` works with its inbox.

## See what people are building.

Public computers appear here as working examples. Open a tile to visit its `name.cool.computer` address. A computer joins the gallery only when its owner shares it.

## Everything that comes with it.

### One name

The address and the inbox are the same name, and they stay with the computer for life: `name.cool.computer` on the web, `name@mail.cool.computer` in the mail.

### Agents included

Claude Code and Codex come pre-installed and run with your own accounts. They can add tools, change files, run commands, and keep services available at `name.cool.computer`.

### Persistent by default

Your files and installed tools remain saved between sessions. A request to `name.cool.computer` reaches its configured service automatically.