# Claude — computer use in Cowork and Claude Code
The phone requests, the desktop executes, and the result returns to the phone. Preserve the same direction in every cycle so different tasks share one visual language.
```motion-demo
{
"id": "sequence",
"title": "Overall choreography",
"src": "demos/sequence.html",
"duration": 73.333333,
"status": "authored",
"description": "Motion and composition example",
"initialTime": 22,
"params": [
{
"key": "title",
"label": "Sample main copy",
"type": "text",
"value": "Reach your desktop",
"maxLength": 60
},
{
"key": "accent",
"label": "Accent color",
"type": "color",
"value": "#ba5d44"
}
],
"presets": [
{
"label": "Default content",
"values": {
"title": "Reach your desktop",
"accent": "#ba5d44"
}
},
{
"label": "OpenDesign adaptation",
"values": {
"title": "OpenDesign",
"accent": "#7050da"
}
}
]
}
```
## Fix the two endpoint roles
Sand background, white phone and desktop devices, brick-red request bubbles, and fine connections.
Complete each task through phone request → desktop execution → phone confirmation, repeating this structure three times with progressively developing content.

## Focus on the request before revealing execution
Place the phone on the left and execution environment on the right; thin connections express causality, not decorative trajectories.
Focus on input first, pull back to show both endpoints, then move closer to the returned result.
```motion-demo
{
"id": "clip-2",
"title": "Focus on the request before revealing execution",
"src": "demos/clip-2.html",
"duration": 10,
"status": "authored",
"description": "6–16 seconds · Motion example",
"initialTime": 0.6
}
```
## Repeat the cycle, change the task
Each round starts on the phone, moves to computer execution, and returns to the phone for results. Replace content across three tasks while keeping direction and device positions fixed.
| Time | Section |
|---|---|
| 0.00–6.00s | Short task-context statement |
| 6.00–12.00s | Phone request |
| 12.00–14.00s | Phone and computer side by side |
| 14.00–20.00s | Export the document |
| 20.00–25.00s | Add calendar attachment |
| 25.00–28.00s | Return result |
| 28.00–34.00s | Second request |
| 34.00–43.00s | Run and capture screenshot |
| 43.00–47.00s | Phone receives screenshot |
| 47.00–53.00s | Third request |
| 53.00–65.00s | Batch-process images |
| 65.00–70.00s | Export result |
| 70.00–73.33s | Brand closing frame |
## Replace the cross-device tasks
For creative tools, show remote request→desktop generation→phone review, keeping endpoint roles consistent.
Task count may vary, but each needs a cause, process, and result; do not merely swap static device images.
## Color and typography
Sand background, white phone and desktop devices, brick-red request bubbles, and fine connections.
#e1d9ca · #20211d · #ba5d44 · #c5d5cb · #ffffff
## Elements and production rules
Phone request endpoint / Desktop execution endpoint / Connection line / Request bubble / Operation window / Returned result card
- Complete each task through phone request → desktop execution → phone confirmation, repeating this structure three times with progressively developing content.
- Place the phone on the left and execution environment on the right; thin connections express causality, not decorative trajectories.
- Focus on input first, pull back to show both endpoints, then move closer to the returned result.
## Content replacement
- For creative tools, show remote request→desktop generation→phone review, keeping endpoint roles consistent.
- Task count may vary, but each needs a cause, process, and result; do not merely swap static device images.
## 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": "Anthropic",
"id": "V238",
"palette": [
"#e1d9ca",
"#20211d",
"#ba5d44",
"#c5d5cb",
"#ffffff"
],
"typography": "Sand-colored background, white phone and desktop devices, brick-red request bubbles and thin connectors",
"sample": "Reach your desktop",
"objects": [
"Phone request endpoint",
"Desktop execution endpoint",
"Connection line",
"Request bubble",
"Operation window",
"Returned result card"
],
"frames": [
{
"path": "assets/reference-1.jpg",
"timeSeconds": 0.0,
"frameId": "K0001",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-2.jpg",
"timeSeconds": 12.0,
"frameId": "K0024",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-3.jpg",
"timeSeconds": 25.0,
"frameId": "K0055",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-4.jpg",
"timeSeconds": 34.0,
"frameId": "K0075",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-5.jpg",
"timeSeconds": 53.0,
"frameId": "K0123",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-6.jpg",
"timeSeconds": 70.0,
"frameId": "K0175",
"role": "reference-evidence",
"status": "measured"
}
],
"stages": [
{
"start": 0,
"label": "Short task-context statement",
"end": 6,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 6,
"label": "Phone request",
"end": 12,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 12,
"label": "Phone and computer side by side",
"end": 14,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 14,
"label": "Export the document",
"end": 20,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 20,
"label": "Add calendar attachment",
"end": 25,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 25,
"label": "Return result",
"end": 28,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 28,
"label": "Second request",
"end": 34,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 34,
"label": "Run and capture screenshot",
"end": 43,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 43,
"label": "Phone receives screenshot",
"end": 47,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 47,
"label": "Third request",
"end": 53,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 53,
"label": "Batch-process images",
"end": 65,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 65,
"label": "Export result",
"end": 70,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 70,
"label": "Brand closing frame",
"end": 73.333333,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
}
],
"duration": 73.333333,
"fontFamily": "Arial, sans-serif"
}
```