How it works
PageWell has no editor. Your agent writes files, the CLI syncs them, a link comes back. Everything below is what happens between those two moments.
The CLI opens a device flow: it prints a short code, you approve it in a browser you are already signed into. The agent never approves its own login — the approve endpoint accepts a session cookie and nothing else, so a token cannot mint another token.
$ pagewell login
open https://pagewell.ai/device and enter
JHQT-2W9D
✓ signed in as mira@example.com
plan compares local hashes against the server and writes nothing. upload sends only the blobs the server does not already have, addressed by sha256. commit applies the whole manifest under one idempotency key — so re-running an interrupted push is a no-op, not a duplicate.
$ pagewell push ./docs
plan 12 files · 3 changed · 0 deleted
upload 3 blobs · 1.2 MB
✓ commit rev 41 (idempotent)
# run it again
$ pagewell push ./docs
✓ nothing to do
Four visibilities, and they are not a slider. Expiry is set at creation. Links you already handed out keep working when you change plans, and going over quota pauses new writes rather than breaking what is already published.
publicindexed, listed on Discover and your profileunlistedanyone with the URL — never listed anywherecodesix characters, case-sensitive, expires when you saidpassworda phrase on top of the linkMapping
None of this is configuration. These are conventions read off the directory as it is found, so an agent can predict the published URL without asking us.
01-guide/a section — the prefix sets order and leaves the URLindex.mdthat level's landing page*.mda document, with a table of contents*.htmlserved as written — sandboxed if it carries a script_assets/referenced files; never gets a page of its ownllms.txtwritten by us — the whole site in one fetchFor agents
Install the SKILL and the agent gets the CLI plus the rules it needs. Two of those are hard limits on our side, not advice in a prompt:
No token scope grants billing writes. There is no billing:write to request — an agent that decides to upgrade your plan gets a 403, not a charge.
The device-approve endpoint accepts a session cookie and nothing else. A token cannot widen itself into another token.