Claude Code on a laptop

description.yaml is AWML 0.4, as it was pushed. The fit reads it converted to AWML 0.8.

# Claude Code on a person's own laptop, started on a schedule by Claude Desktop's local scheduled
# tasks, or by cron or launchd running `claude -p`. This describes a kind of platform, not anyone's
# machine. To describe your own laptop, copy this file and add what else runs there, such as other
# coding agents, and the folders you keep. Checked against Anthropic's documentation on 22 October
# 2026.
awml: "0.4"
platform: { id: claude-code-laptop, label: "Claude Code on a laptop" }

# A laptop may be shut for a fortnight's holiday, as in the AWML spec's own example. Desktop's local
# scheduled tasks fire only while the app is open and the computer is awake, and a run missed while
# it slept is caught up once on waking, and only from the last seven days. A laptop that never
# sleeps can say less.
# https://github.com/chrismdp/awml/blob/main/SPEC.md#placing-a-workflow-where-it-can-run
# https://code.claude.com/docs/en/desktop-scheduled-tasks#how-scheduled-tasks-run
# https://code.claude.com/docs/en/desktop-scheduled-tasks#missed-runs
off_for_up_to: P14D

# Each run is a Claude Code session that carries out the task's instructions.
# https://code.claude.com/docs/en/desktop-scheduled-tasks
# https://code.claude.com/docs/en/headless
steps: agent

# Claude Code's own agent, on the Claude API or a Claude subscription by default. If you route it
# through Amazon Bedrock, Google Cloud or Microsoft Foundry, that company processes the content on
# its own terms, so list it here in place of anthropic.
# https://code.claude.com/docs/en/authentication
# https://code.claude.com/docs/en/third-party-integrations
agents: [anthropic]

# Claude Code's sandbox is off by default, so the shell commands it runs use the laptop's own network
# and code can call any model company's API with a key it is given. Turning the sandbox on narrows
# this to the hosts you allow.
# https://code.claude.com/docs/en/sandboxing
calls: any

# A laptop holds its owner's folders. A shared description cannot know their names, so it says
# notes, as AWML's examples do: keep a workflow's contexts under notes, or name your own folders
# when you describe your own laptop.
# https://github.com/chrismdp/awml/blob/main/SPEC.md#placing-a-workflow-where-it-can-run
holds: [notes]