Command line
Run your automations from the terminal
awl is the Autoworklet command-line client. Sign in once, then list, run and schedule your organization's worklets, or start a cloud computer and drive it from a shell script or a CI job.
Install
curl -fsSL https:/The script downloads the latest release for your machine, verifies its SHA-256 checksum and makes sure it starts before it puts awl in ~/.local/bin. It never asks for sudo. It adds that directory to PATH in your shell profile, so open a new terminal when it finishes. Run the same command again to update.
- macOS: Apple silicon. There is no build for Intel Macs.
- Linux: x86_64 with glibc 2.17 or newer. Alpine (musl) is not supported.
- Windows: Run the installer inside WSL.
Windows without WSL: download https://autoworklet.com/awl/<version>/awl-<version>-windows-x64.zip, where https://autoworklet.com/awl/latest names the current version.
Options
Options go after bash -s --, for example to install a particular release:
curl -fsSL https:/| Option | What it does |
|---|---|
| --version X.Y.Z | Install that release instead of the latest one. |
| --dir DIR | Install into DIR instead of ~/.local/bin. |
| --no-modify-path | Leave your shell profile alone; add the directory to PATH yourself. |
| --dry-run | Print what would be downloaded and where, then stop. |
| --uninstall | Remove awl, its license notices and the PATH line the installer added. |
Sign in
awl login opens your browser to sign in to your Autoworklet account.
On a server or in CI there is no browser. Create a CLI service token on your profile (CLI service tokens). It signs awl in as you, starting in the organization you pick. Pipe it in once and awl keeps the session:
awl login --service-token - < awl-token.txtOr set AWL_SERVICE_TOKEN for a single job. Each command signs in with it, and nothing is saved to disk:
export AWL_SERVICE_TOKEN=awlst_... # from your CI secrets
awl worklet listFirst commands
The installer prints these when it finishes.
| Command | What it does |
|---|---|
| awl login | Sign in through the browser. |
| awl login --service-token - | Sign in without a browser, on a server or in CI: pipe in a token from your profile. |
| awl doctor | Check what this machine is ready for. |
| awl worklet list | List your organization's worklets. |
| awl --target modal up | Start a cloud computer to drive from this terminal. |
More commands
| Command | What it does |
|---|---|
| awl worklet run WORKLET_ID --wait | Run a worklet in the cloud and wait until it finishes. |
| awl worklet runs WORKLET_ID | List its recent runs. |
| awl create ./my-worklet | Create a draft cloud worklet from a worklet folder on your machine. |
| awl --target modal screenshot | Take a screenshot of the cloud computer. |
| awl --target modal down | Shut the cloud computer down. |
The awl worklet commands are list, get, push, publish, run, runs, schedule and email. awl --help lists every command, and awl COMMAND --help explains one. awl drives your worklets and cloud computers; it does not automate the computer it runs on.
Using a coding agent instead? Connect it over MCP.
Update and uninstall
Run the install command again to update to the latest release. To remove awl, its license notices and the PATH line the installer added:
curl -fsSL https:/If you installed with --dir, pass the same --dir to update and to uninstall. Your sign-in stays in ~/.autoworklet; delete that directory to remove it too.
License
awl is proprietary software, provided under our Terms of Service. Each release archive includes THIRD_PARTY_NOTICES.txt, the licenses of the open-source software inside it, and the installer keeps a copy at ~/.local/share/awl/THIRD_PARTY_NOTICES.txt.