# Perplexity Computer now works in email
Use email as both task entry and result exit. One send begins the work; one reply returns an openable file.
```motion-demo
{
"id": "sequence",
"title": "Overall choreography",
"src": "demos/sequence.html",
"duration": 41.508133,
"status": "authored",
"description": "Motion and composition example",
"initialTime": 8,
"params": [
{
"key": "title",
"label": "Sample main copy",
"type": "text",
"value": "Computer works wherever you do",
"maxLength": 60
},
{
"key": "accent",
"label": "Accent color",
"type": "color",
"value": "#63a89d"
}
],
"presets": [
{
"label": "Default content",
"values": {
"title": "Computer works wherever you do",
"accent": "#63a89d"
}
},
{
"label": "OpenDesign adaptation",
"values": {
"title": "OpenDesign",
"accent": "#7050da"
}
}
]
}
```
## Explain the task and attachment in the draft
Establish the mailbox context before opening a new email. Show request and attachment together, keeping send near the focus; subject and attachment names should directly explain the task.

## Allow processing time after sending
Close the draft after send, then show attachment processing and execution. Do not show completed outputs before sending; processing may be brief but needs at least one state change.
```motion-demo
{
"id": "clip-2",
"title": "Allow processing time after sending",
"src": "demos/clip-2.html",
"duration": 11,
"status": "authored",
"description": "11–22 seconds · Motion example",
"initialTime": 0.6
}
```
## Return along the same task chain in the reply
Bring execution results back by email, open the deliverable, then return to the workspace. Keep a recognizable link between reply subject, filename, and initial attachment so it does not feel unrelated.
| Time | Section |
|---|---|
| 0.00–4.00s | Statement |
| 4.00–8.00s | Mailbox |
| 8.00–11.00s | New email |
| 11.00–15.00s | Enter request |
| 15.00–18.00s | Send |
| 18.00–22.00s | Process attachment |
| 22.00–29.00s | Email reply |
| 29.00–33.00s | Open output |
| 33.00–37.00s | Return to workspace |
| 37.00–41.51s | Brand |
## Set the familiar mailbox against deep green
Use deep green and pale outer text while keeping the email body bright and compact. Serif may serve branding statements, with sans serif subjects, addresses, and body; reserve accents for send, status, and result entry.
## Replace the whole email, not just its subject
Change recipient, request, input attachment, and returned file. Budgeting, design checks, and data cleanup fit this flow; the email must explain why the later output is produced.
## Color and typography
Serif proposition headings with sans serif interface text; generous whitespace and fine borders.
#08332e · #ecf4ed · #63a89d · #154943 · #ffffff
## Elements and production rules
Mailbox window / email draft / attachment / execution steps / reply / spreadsheet output
- Trigger the task by email and return results to the same thread; attachments are input dependencies.
- Show processing only after sending, and open outputs only after the reply.
## Content replacement
- Replace email tasks and deliverable files; preserve send→execute→reply.
## Production parameters
[Visuals and objects](style.json) · [Section timing](timeline.json) · [Position data](tracks.json) · [File manifest](manifest.json)
This specification is based on the reference video. The HTML provides editable choreography examples; each file identifies the source, precision and valid interval of its data.
```motion-board
{
"version": 1,
"brand": "Perplexity",
"id": "V259",
"palette": [
"#08332e",
"#ecf4ed",
"#63a89d",
"#154943",
"#ffffff"
],
"typography": "Serif message headings with sans-serif interface text, ample negative space and thin borders",
"sample": "Computer works wherever you do",
"objects": [
"Mailbox window",
"Email draft",
"Attachment",
"Execution steps",
"Reply",
"Spreadsheet output"
],
"frames": [
{
"path": "assets/reference-1.jpg",
"timeSeconds": 0.0,
"frameId": "K0001",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-2.jpg",
"timeSeconds": 8.008000000000001,
"frameId": "K0016",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-3.jpg",
"timeSeconds": 15.015,
"frameId": "K0029",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-4.jpg",
"timeSeconds": 18.018,
"frameId": "K0035",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-5.jpg",
"timeSeconds": 29.029,
"frameId": "K0054",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-6.jpg",
"timeSeconds": 37.037,
"frameId": "K0074",
"role": "reference-evidence",
"status": "measured"
}
],
"stages": [
{
"start": 0,
"label": "Statement",
"end": 4,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 4,
"label": "Mailbox",
"end": 8,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 8,
"label": "New email",
"end": 11,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 11,
"label": "Enter request",
"end": 15,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 15,
"label": "Send",
"end": 18,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 18,
"label": "Process attachment",
"end": 22,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 22,
"label": "Email reply",
"end": 29,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 29,
"label": "Open output",
"end": 33,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 33,
"label": "Return to workspace",
"end": 37,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 37,
"label": "Brand",
"end": 41.508133,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
}
],
"duration": 41.508133,
"fontFamily": "Georgia, serif"
}
```