Docs / Getting started

dawn CLI

dawn is the command-line client for Dawnrose. It deploys the folder you are in, streams build and runtime logs, manages variables and domains, and runs local commands with a service’s variables. It needs Node.js 22 or later, and tar for dawn up.

Install

Install it with npm. The package is served from this site, not from the npm registry.

npm install -g https://dawnrose.ai/sdk/dawnrose-cli-0.1.0.tgz

To check the download before installing, fetch it, check its SHA-256, then install the file you checked. On Linux, use sha256sum -c in place of shasum -a 256 -c.

curl -fLO https://dawnrose.ai/sdk/dawnrose-cli-0.1.0.tgz
echo "b97bef28ebc1e74d16e595740a2dc091710ee6e4dc02c20af2c85006c65a518b  dawnrose-cli-0.1.0.tgz" | shasum -a 256 -c
npm install -g ./dawnrose-cli-0.1.0.tgz

Then dawn --version prints the version, and dawn help lists the commands. dawn help <command> shows the flags and examples of one.

Log in

Create a token under Account → Tokens (or an agent token on the Connect agent page), then:

dawn login --url https://app.dawnrose.ai --token drt_…

dawn login checks the token and saves the URL and token to ~/.dawnrose/config.json with mode 0600. Without --token in a terminal, it asks for both. Later commands use the saved URL.

In CI, set DAWNROSE_URL and DAWNROSE_TOKEN instead of running dawn login.

Projects and linking

Most commands act on the project, environment and service linked to the current directory. The link lives in .dawnrose/link.json, found by walking up from the current directory like git does. Add .dawnrose to .gitignore; the CLI reminds you when it is missing.

Deploy

dawn up respects .gitignore and .dawnignore files at every level and always skips .git, node_modules and .dawnrose. The compressed upload can be up to 100 MB on Trial and 500 MB on Hobby and Pro. If the directory has no linked service, dawn up asks which service to deploy to or creates a new one named after the directory, with a public domain, and links it. If the target service deploys from a repository or image, the upload replaces that source for this deployment only.

Deploy commands exit with a non-zero code unless the deployment succeeds. Press Ctrl+C to stop following the logs; the deployment continues on the server.

dawn up
dawn up ./web --service web --detach -m "try new cache"
dawn deploy --all

Logs and metrics

dawn logs -f --filter '@level:error'

The filter syntax is described in Logs, metrics and alerts.

Variables and local commands

With --shared, vars set and vars unset deploy every service whose configuration changed. Sealed variables are never sent to your machine, so vars pull, run and shell leave them out and print a warning.

dawn vars set NODE_ENV=production
dawn vars set API_KEY=s3cr3t --sealed
dawn vars set --skip-deploy < .env
dawn vars pull > .env
dawn run -- npx prisma migrate deploy

Services and networking

dawn exec -- 'ls | wc -l'
dawn exec --service api -- npx prisma migrate deploy
dawn domain app.example.com

A single argument after -- is passed to the shell verbatim, so pipes work when you quote the whole command.

MCP bridge

Other commands

• dawn completion bash|zsh|fish prints a shell completion script, for example source <(dawn completion bash).
• dawn help [command] shows help.
• dawn version prints the CLI version.

Global flags

Exit codes

dawn exec exits with the command’s own exit code, or 124 if it timed out. dawn run and dawn shell exit with the local command’s code.