The Dropway CLI

curl -fsSL https://raw.githubusercontent.com/danielpang/dropway/main/install.sh | sh

The script installs to /usr/local/bin (falling back to ~/.local/bin). Set DROPWAY_INSTALL_DIR to choose another location, or DROPWAY_VERSION to pin a specific release.

Prefer to build from source? Install it with Go instead (this puts a dropway binary under $(go env GOPATH)/bin):

go install github.com/danielpang/dropway/cli/cmd/dropway@latest

Either way, check it worked:

dropway version

dropway login

The CLI opens your browser to the Dropway sign-in page (the same account you use in the dashboard). After you approve, it saves your credentials to ~/.config/dropway/credentials.json. That’s it, no tokens to copy. Sign out any time with dropway logout.

export DROPWAY_API_KEY=dw_...
dropway deploy ./dist --new --site my-docs --send

Self-hosting? Point the CLI at your own instance with --api (or the DROPWAY_API environment variable); it defaults to the hosted https://api.dropway.dev. dropway login honors the same flag.

dropway login --api http://localhost:8080   # self-host

Without --send it is a dry run: it prints the manifest it would upload and makes no network calls. Add --send to actually deploy (run dropway login first, or set DROPWAY_API_KEY).

Preview a deploy (dry run, no upload)

dropway deploy ./dist

Create a new site and deploy to it

dropway deploy ./dist --new --site my-docs --send

This creates the my-docs site, uploads the folder, and prints something like https://my-org--my-docs.dropwaycontent.com.

Upload a folder to an existing site

dropway deploy ./dist --site-id 1a2b3c4d --send

Only files whose contents changed are uploaded (everything is content-addressed), then the new version is published. Roll back any time from the dashboard.

Deploy to a self-hosted instance

dropway login --api http://localhost:8080
dropway deploy ./dist --api http://localhost:8080 --new --site demo --send

dropway sites lists the sites you own. Add --all to list every site in your organization, with an owner column.

dropway sites          # sites you own
dropway sites --all    # every site in the org

Read a site over HTTP

dropway read fetches served content and writes it to stdout, so you can pipe it elsewhere. Pass a full URL, or a site slug the CLI resolves to its live URL first.

dropway read my-docs
dropway read https://my-org--my-docs.dropwaycontent.com

Public sites need no sign-in. A gated site returns its sign-in page instead of the content, since the fetch is a plain HTTP request.

dropway chat share reads a conversation export (Claude Code JSONL, a ChatGPT JSON export, or plain text) and publishes it to your organization’s chat library. Add --site to attach it to a site, where it becomes that site’s “How this was made” panel under the site’s own access control.

# share a Claude Code session, attached to a site
dropway chat share ./session.jsonl --site my-docs --source claude_code

# condense the transcript's tool activity into action annotations
dropway chat share ./session.jsonl --site my-docs --derive-actions

Append as the work continues

dropway chat append adds a follow-up message, an action annotation, or another export to an existing log, by chat id or by --site. Action annotations record a file edit or a tool run with a one-line note on why.

dropway chat append --site my-docs --message "Reworked the hero copy"
dropway chat append --site my-docs --action file_edit --path index.html --comment "Tightened the headline"

New sites start at your organization’s default visibility (org-only). To make a site public, password-protected, or limited to an email allowlist, change its access in the dashboard, or use the set_site_access tool on the Dropway MCP server.