deploy.wgw.lol

Stop sending screenshots. Send the thing.

WGW Deploy turns static output into a public URL from the terminal. The latest link keeps moving. The pinned link keeps the exact deploy alive for the work that needs a record.

One terminal state change
$ npx wgw-deploy

dist/                      local files
careful-fall-mqstr7zz      generated project
latest                     https://careful-fall-mqstr7zz.wgw.lol/
pinned                     https://careful-fall-mqstr7zz--26704cb219eb67f3.wgw.lol/
Default
dist from current cwd
Domain
CNAME shown when needed
Agents
--skill, --json, --list

The build is done. The handoff is not.

A static folder is useful only after someone can open it. WGW Deploy cuts the dead space between finished files and a link in the thread.

1
npm run build

dist/

The app already became files. Do not make the reviewer rebuild it.

2
npx wgw-deploy

latest + pinned

Default deploy picks up dist and publishes it to a generated wgw.lol project URL.

3
npx wgw-deploy --domain review.example.com

named URL

When the artifact needs a memorable address, assign a WGW subdomain or external hostname.

4
npx wgw-deploy --list --json

local state

Inspect project hashes, cwd and dir ownership, URLs, and expiration dates before touching state.

5
npx wgw-deploy --delete

clean exit

Remove the local and remote project when a temporary preview no longer needs to exist.

Demos, repros, docs, reports. Same exit door.

WGW Deploy does not ask what framework made the files. It takes the static output and gives back URLs that fit the next conversation.

generated docslatest
broken repropinned
client demolatest
audit evidencepinned
throwaway previewdelete
$ npx wgw-deploy --skill
prints when to deploy
prints which URL to return
prints what not to upload

$ npx wgw-deploy --list
reads local project state before acting

Give the agent a deploy reflex.

Install the deploy reflex with npx wgw-deploy --skill.

Deploy generated output instead of explaining where it lives.

Return both URLs when the CLI prints both.

Use pinned links for exact evidence and latest links for moving review.

Keep secrets out of the deployed folder.

If the preview survives, name it.

Start with a generated WGW domain. Move to a named WGW subdomain or external hostname when the artifact needs a stable public address.

$ npx wgw-deploy --domain launch-preview
url https://launch-preview.wgw.lol/

$ npx wgw-deploy --domain docs.example.com --json
dns CNAME docs.example.com -> cname.wgw.lol

$ npx wgw-deploy --delete-domain

Build files. Publish them. Hand back the URL.