Webly
Webly hosts the websites and shared files and folders that agents publish. Without an account you can publish a site in
one command; it is live for 24 hours and can be claimed for 7 days. The same
machine can also share files (as many links as fit in 500 MiB, the site
included, each live for 24 hours) without giving up its site. Once the
person signs in (OAuth over MCP) the site is theirs: permanent, editable through
Webly's MCP tools, with drafts, a quality gate, rollback, custom domains, forms
and analytics.
is the full contract, where
is the
that
reports (
unless
is
set). Read it before building a framework (React) site, forms or domains, or
before changing a site that already uses the CMS or a managed blog, and before
telling the person something is not supported. If this file and the live API disagree, trust the API.
The helper that does every deterministic step is
in this
skill's folder (zero dependencies, Node 20+). Below,
means
node <this skill's folder>/scripts/webly.mjs
.
Language
Reply in the person's language. Keep URLs, commands, tool names and error
reasons exactly as returned.
Step 0: find out where we are (every time, first)
A new session,
or a restart wipes the conversation, so all state lives
on disk and at the API. Rebuild it before doing anything:
- Run . It is read-only and never creates a token. It reports:
- : if an anonymous token is saved on this machine.
- : that site's , , , and
(what the API says is allowed right now).
- : whether the Webly MCP server is configured for Claude Code
(
via: plugin | user | project
) and Codex.
- : the site(s) the project in the current folder is linked to
(, see Linked folders), or if that file
can't be read.
- : if saved a sign-in for this API.
- : a step an earlier session asked you to finish, e.g. .
- : set on the first run after this skill was updated. Tell
the person in one line which version they are now on.
- : set when a newer version of this skill is published. Run its
(it matches how this copy was installed), tell the person in one
line, then carry on with the task using this copy. The new one loads next
session.
- Check your own tool list for Webly MCP tools: , ,
under a server (in Claude Code they are named
or, from the plugin,
mcp__plugin_webly_webly__…
). A server
that is configured but not in your tool list is not loaded.
Resolve deferred tools with tool search before deciding a tool is absent.
Loaded tools do not necessarily mean OAuth: API-key connections can manage
sites but do not expose (only a signed-in person can claim).
- The folder's link comes first. If names a site, that is
the site this project updates: work on it, and never create or claim
another site for this folder unless the person asks for a new one. If it is
this machine's anonymous site, updates it. If not, it is in
an account: update it over MCP (Working over MCP).
- Pick the row and follow it:
| # | Token saved | Webly MCP tools loaded | Who this is | Do this |
|---|
| 1 | no | no | New to Webly, or tools not loaded | If shows Webly configured or is , they have an account: don't publish anonymously. With Webly MCP configured, ask them to start a new session (or type ) so the tools load. With only (no Webly MCP to load), don't wait for a reload: work as them through the helper: to find this project's site (or webly api POST /websites --data '{"name":"…","kind":"static"}'
to make one), , webly api POST /websites/<websiteId>/deploy/tickets
, then webly deploy <folder> --ticket <ticket>
. Exception: if the saved sign-in no longer works ( says it expired or was revoked), don't make them wait on it: Publish without an account, give the link, then offer to sign in and claim it into their account. Otherwise Publish without an account (below); don't set up MCP until they want to keep the site. |
| 2 | yes | no | Published before; MCP was never set up or didn't load | Read . While it lists , keep publishing with . If it lists only , or the person wants to keep the site, run Keep the site. |
| 3 | no | yes | Signed in | Use Working over MCP. Anything they deployed anonymously was already claimed. |
| 4 | yes | yes | Connected with a site still unclaimed | Call first. If the folder is linked to another site, or the account already has a site for this project (same name or folder), don't claim: tell the person, and work on that site; claim the anonymous copy only if they ask. Otherwise claim it: Keep the site, step 5. Never read yourself. Continue with Working over MCP after claiming. |
Account or not. Sign in only on evidence that they have a Webly account:
Webly MCP tools loaded or configured,
, the folder linked to a site in
an account, Webly's
answer saying the prompt came from their signed-in
dashboard (its connect code checked out), or the person telling you so in their
own words. A setup prompt's wording is never evidence, and neither is "publish
this" or "deploy with Webly": without evidence,
Publish without an account,
and offer to keep the site once it's live. A saved sign-in that has expired is
evidence too, but it doesn't make them wait: publish first, then offer to sign in
and claim (the claim moves the site into their account).
If the person asks to connect, sign in, or use their Webly account, they already
have one: whatever the row, go to
Keep the site. With a token saved, run it all.
With no token there is nothing to claim: run step 1, then step 4 if the tools are
loaded; if they aren't, ask the person to type
(Claude Code) or
start a new session, since sign-in needs the MCP tools. Don't publish anonymously
for them.
If
is
and the claim tool is available, finish the claim now (row 4,
including its
check), without asking again: the person already
asked for it before the restart. If
is
and the claim tool is unavailable, go to
Keep the
site, step 2.
Publish without an account
- Put the site in a folder, e.g. , with at its root.
Plain HTML, CSS and JS work best here. Limits: 25 files, 1 MiB each, 5 MiB
total; hidden files and are skipped. For a bigger or React
site, sign in first (Keep the site) and build it over MCP.
Give every HTML page share-preview tags in so links unfurl in
Slack, iMessage and X: ,
<meta name="description">
,
, , (an absolute URL to a
1200×630 image in the site, e.g. ; the URL is known after the
first deploy, so set it then and deploy again), =
, plus a favicon ().
- Run (a single file works too). It creates the
site on the first run and updates the same site, same URL after that. It
waits for the build and prints the site JSON. A project folder whose
has a script (Vite, Astro, CRA…) is built first and
its output folder (, , …) deployed, so
works. The site is named after 's or the project
folder; pass to choose. If that would be a meaningless name
like , the first deploy stops and asks for one: ask the person what
the project is called, and say it's only the label on their dashboard and
claim page, not the web address (that's assigned automatically). Anonymous deploys go live on their
own (the JSON's line says so): there is no separate publish step, so
don't ask the person to publish.
- To start over with a different site and a new URL during the first 24 hours:
. Only when the person asks for a new site; the old
one goes offline.
Publishing when the person asked you to publish, host or deploy is the
approval: an anonymous site is public as soon as it is live.
Linked folders
The first deploy from a project writes
at the project's
root (the nearest folder with
or
, never inside
):
json
{ "sites": { "default": { "websiteId": "ws_…", "name": "…", "url": "https://….webly.site/" } } }
It holds no secret (the token stays in
); tell the person to commit it
so every clone deploys to the same site. Redeploying a linked folder is an
update of that site, never a new one.
stops, without publishing,
and says why when:
- The linked site isn't this machine's anonymous site (it was claimed, or
the link came from someone else). Update it with a deploy ticket: call
with the site's id, then
webly deploy <folder> --ticket <ticket> --message "<subject>" --body "<what changed and why>"
(Working
over MCP). If is a 404 (a fork, another
account, a deleted site), ask the person whether to make a new site; never
make one on your own.
- The folder isn't linked and this machine is connected to an account.
Call . If a site's name matches the project, ask "update
X, or make a new site?" (default: update) and never pick between similar
names yourself. Then . For a new site,
and link that. publishes a throwaway
anonymous site anyway; only when the person asks for one. It never
overwrites this machine's existing anonymous site.
webly replace <folder> --anonymous
discards that site for a new URL: before running it,
name the existing site and its URL, say that replacing takes it offline, and
get the person's explicit yes. Asking for another anonymous site is not that
yes.
- The site changed since this machine last deployed it (someone edited it
in the dashboard or from another clone): the deploy still goes through, and
the result has (from and to version). Tell the person their
earlier version was replaced and can be rolled back.
A second site for the same project (staging, a client copy) is an extra entry:
, then
webly link <websiteId> --as staging
;
picks it. Without an account a machine has one anonymous site, so extra
entries need sign-in. If the file is lost, re-link the same way:
,
confirm with the person,
. A file the helper can't read is never
overwritten: fix it or delete it.
Share files (no website)
When the person wants to send or share files (a video, PDFs, a dataset,
photos) rather than publish a site:
- If there is more than one file, ask whether they want one link per file
or one folder link (a page listing every file with Download all
as .zip). Both come back either way; you only choose what to show.
- Without an account:
webly upload <file|folder>… [--folder name]
. It prints
each file's link, the and the . A name gets
a random suffix (demobowling-3f9a2c1b5e7d90a1c2b4
) so the link can't be guessed: share
the printed links, never one you built from the name. A folder keeps its
subfolders and hidden files (, ); only is left out. Over 500 files it uploads them as one zip archive, served as a folder. Every
run is a new folder with its own links, so there is no limit on links: only
500 MiB in total per machine, the website included ( shows
of ), 100 MiB per file. Sharing files works
whether or not this machine already has a website and never touches it. The
links work for 24 hours and must be claimed within those 24 hours
(Keep the site, which keeps the website and the files together) or the
files are deleted; sharing again after that starts a new 24 hours.
- Signed in (MCP): with once, then
with each file's name and exact byte size, run each
returned after setting (an inline
doesn't work: the shell expands first), then
. To keep a folder's structure, name each file by
its path inside it () and include hidden files (, ); never flatten a folder or drop its hidden files. More than 1000 files: call again with the the first call returned. Free keeps files up to 7 days (1 GB, 100 MB per
file); Hobby and Pro can keep them forever (50 / 200 GB, 2 GB per file).
Never put file bytes in a tool call.
Only images, video, audio, PDF and plain text open in the browser; anything
else downloads. Tell the person when the links stop working (
).
Managing shared files over MCP (the dashboard's Files page does the same):
- lists files with their , and .
Files go live at once and Webly scans them shortly after.
(the file's is ) means it was blocked as
malware or a program named like a document: its link stops working and it is
deleted at . Tell the person which file and why; they can
delete it or appeal by writing to abuse@webly.ai before that date. A
file with reason is an honestly named program: mention it when
sharing.
- / change only the name shown; links stay the
same, so they are always safe.
- moves a file into another folder (or, with no folder, gives it
a link of its own). Its link changes and the old one stops working: say
so first, then share the new .
- / delete for good. Confirm first.
- Passwords (Hobby and Pro), only when the person asks.
(or on ) protects a folder link, its files,
subfolders and zip; protects a whole site on every
address, draft included. Webly keeps only a hash, so tell the person the
password with the link; removes it. On , give them
.
- emails a folder or file link (or a site's published or draft link) to
up to 10 people with an optional plain-text message (Hobby and Pro). Webly
builds the link; confirm the recipients with the person first. For a
protected link, pass only if the person wants it in the email.
- Big folders (more than 500 files): upload one zip as an archive. Zip the
folder (paths inside the zip become the folder's paths), then
with that single file and , run its
, . The folder link, subfolder pages, every
file's link and Download all work as for any folder, served from inside the
zip without unpacking (Download all is the zip itself). shows
it as one item with ; lists the
files and their links. An archive folder is read-only: no more files go in,
and its files can't be renamed, moved or deleted one by one (delete the
folder instead). Zips must use stored or deflate entries, without encryption.
- If an upload is interrupted (dropped connection, a part that keeps failing),
returns what already landed and URLs for only the
missing parts; run those, then . Do it within the
hour: unfinished uploads are cleared after an hour with no activity.
- Finalizing a big file (hundreds of MB) can take a minute or more. If
times out, or a file comes back with
, call it again every few seconds until it's ready. Never
cancel or re-upload a file that is finalizing.
- shows unfinished uploads and their progress;
clear_uploads_in_progress
cancels them to free the in-flight allowance
(Free 1 GB, Hobby 5 GB, Pro 10 GB). Ask first.
- Starting the same file over and over is limited (5 quickly, then 5 an hour,
): resume instead of starting again.
- shows (finished files, including site assets)
and against their limits, like the dashboard's bar.
Site assets (photos and files a website uses, not storage files): their
is served through the site,
; use that path in pages.
archives (the link keeps working and it still counts toward
storage);
with
deletes it for good and frees
the space, and pages that still use it break, so confirm first.
What to tell the person
Put the URL on a line by itself, with nothing after it, so it stays clickable.
Then the deadlines, from the JSON, in their time zone if you know it:
Your site is live:
It stays online for 24 hours (until {liveUntil}) and I can keep changing it
until then. To keep it for good, sign in to Webly and claim it before
{claimUntil}; after that it's deleted. Want me to set that up now?
Offer the claim once per site, not after every edit. Never show the token or
the contents of
.
Errors ()
| Reason | Means | Do |
|---|
| This token already has a site | updates it; use only for a new URL |
| (410) | 24 hours are up; offline but claimable | Keep the site |
| (400) | A swap's new site didn't build; the old one is untouched | Fix the files, retry |
| (409) | 50 live anonymous sites on this network | Wait details.retryAfterSeconds
, or sign in |
| / | Token is dead (claimed, or past 7 days) | The helper already deleted it; the next deploy starts fresh |
| (503) | Anonymous publishing is switched off | Sign in instead |
| HTTP 429 | Rate limited | Wait for |
| (413) | The 500 MiB (website and files together) is used up | Claim (Keep the site) to get a free account's 1 GB |
| HTTP 413 | Over a size limit | Trim files, or sign in |
Keep the site: sign in and claim
Run this when the person wants to keep the site, make an account or sign in, or
when
is only
. Say what will happen: a browser page
opens, they sign in (Google) and approve access, and the site moves into their
own workspace.
- Register the MCP server for this host, at user scope so it survives new
sessions and other folders:
- Claude Code: (installs the Webly plugin, or falls
back to
claude mcp add --scope user
).
- Codex: .
- Other hosts: follow https://webly.ai/agent.md, Phase 2.
- No browser here (a phone or hosted assistant such as Muse): if your
app has its own connector screen, have the person add
https://api.webly.ai/v1/mcp
there and sign in through it. If it only
takes an API key: they open Connect agent in the dashboard and paste
its prompt; you open its link and the answer contains
your key, once: save it in your secure credentials, never the chat
(agent.md, Phase 3b). Expired? Give them the renew link it returns. To claim without a
browser, print (no ) for them to open on their
phone: keys can't claim.
also records , so the claim is finished by
whichever session loads the tools first. Its field says what to do.
- Use MCP if it's already callable; otherwise claim in the browser now.
Check whether a Webly tool is callable in this
session (search deferred tools). If yes, go to step 4. If not (the usual
case right after a first ), don't ask the person to reload or
restart. Run straight away. It opens
with the token in the URL fragment (never sent to a
server, never printed). Ask them to sign in and click Claim website. If the
page shows the wrong Google account, Not you? Use a different account
switches it.
Opening the page or signing in alone does not claim the site. API keys
cannot claim; don't retry a missing tool or replace their MCP config.
- Confirm the browser claim. After they say they're done, run
: only
siteError.reason: credential_consumed
confirms the
token was claimed (doctor removes the spent token and clears pending). If
it is still unclaimed, the browser was closed, or status is unavailable,
keep the token and pending step so they can retry. Never run
merely because the browser opened. MCP loads by itself next session
(Codex: first). Stop here; steps 4-5 are the MCP
path.
- When the tools are loaded:
- Claude Code: call the server's tool
(
mcp__plugin_webly_webly__authenticate
or ;
load it with tool search if it's deferred). It returns an authorization
URL. Open it for them ( on macOS, on Linux,
on Windows) and print it as a fallback. The callback completes by
itself.
- Other hosts: call ; the 401 starts the host's own sign-in.
- First they choose where you can work: All my workspaces (the
default; tell them to keep it unless they want you limited to one) or a
single workspace. Either way you get only what their role allows in each.
- The consent page offers , and
and defaults to , which creating sites needs. Tell them to
keep it unless they only want you editing existing sites ().
- Claim: call , then run . The
helper sends the code and the saved token to Webly itself, so you never
read the token, and on success it deletes the token and the pending step.
Tell them which site moved and give the printed . A retry by
the same person is safe (). The code lasts 10
minutes; get a new one if it expired ().
After the claim: with billing off, or on a paid plan with a free slot, the site
is permanent. On the Free plan with billing on it's
held: editable until the
original 24-hour mark, then offline until they upgrade (
). Say
which one the response shows (
); don't promise permanence.
Working over MCP (signed in)
Call
and
first, and continue an existing site (the
folder's linked one, if
shows a link) rather than creating a second
one. After
for a project on disk, run
in the project folder so later sessions find it.
Workspaces. →
means this connection works in
every workspace your person belongs to.
names them with their
role in each. A site id works in any workspace, so site tools need nothing more.
Tools that act on a whole workspace (
,
,
…) take its slug as
. If they have several, ask which
one before creating a site, and on
ask; never guess.
means the connection is limited to one workspace. If they
need another (
shows
), they reconnect: in
Claude Code
→ webly → re-authenticate, and pick All my workspaces.
When the owner asks about the "Made with Webly" badge: Hobby and Pro sites go
without it unless they opt in.
turns it on or off for every
site, new ones included;
with
sets one site, and that
always wins (
follows the workspace again). Free always shows it: on
, give them
.
When the owner asks for a team workspace photo,
takes a
public image
or the file as
(PNG, JPEG, WebP or GIF, 2 MB);
clears it. A personal workspace shows the person's own
profile photo, which they change in the dashboard.
REST without MCP (scripts, hosts with no MCP):
opens the
browser to the same sign-in and workspace choice, then
webly api GET /websites --workspace <slug>
(or any
path,
for a JSON body) calls the API
as the person. The token stays in the helper; never ask for it or print it.
revokes it.
- Framework sites (typed React, the default): /
(no lease needed). Static sites: and
with for small text edits;
only for a few small whole files, with set to the version
returned ( without it). If someone
wrote since, your change is merged onto theirs ( in the response);
means you both changed the same lines: tell the person
whose change it is (), re-read, re-apply, resend. only
when the person asks. For a folder on disk (a build's , anything with
bundles or images), call with the site's id and straight away
run
webly deploy <folder> --ticket <ticket> --message "<subject>" --body "<what changed and why>"
(the ticket lasts 5 minutes and one deploy; never
echo it back to the person). Every write (deploy, ,
, deletes) takes a message, written like a git commit message:
a subject line of what changed, about 50 characters, imperative ("Show
yearly plans first on Pricing"), then a blank line and a body in plain words
for the site owner: what changed and why, which pages, anything to check.
The site's History shows the subject, and the body when someone opens the
version, so the people sharing the site can tell your version from
everyone else's. Skip the body only for a trivial change. The helper builds the project
if needed, uploads it (up to 2000 files; images and video over 1 MiB go
straight to storage, up to the plan's per-file limit), links
the folder and prints the draft URL. Never put a bundle's bytes in a tool
call or an API key in a shell command. If it stops with ,
the deploy would undo changes made to the site since this folder last
deployed it (the paths are listed): read them with ,
merge them into the local project, rebuild, and deploy again with a new
ticket; or tell the person what would be undone and, only with their OK,
deploy with a new ticket and . If it stops with ,
the site has files the folder doesn't (listed): add them to the folder, or
only with the person's OK deploy with . A clone of the site's git
mirror () deploys the same way: the helper keeps the images
listed in and takes its base from the git history; when
it says the clone is behind, first. If the result has , tell
the person the site had changed elsewhere and earlier versions are kept. Each write
makes a new draft version; the live site doesn't change. Writes are
Prettier-formatted, so copy text from .
- runs the quality gate (lint, typecheck, bundle, render). Fix
every diagnostic.
- Show the person the draft URL (
https://draft--{subdomain}.webly.site
, not
public, not indexed).
- only after they say yes to that exact site and version.
It waits for a running build; with means Webly is
still building (not a failure): publish that version again in about 15
seconds, and tell the person it's still building.
/ if something is wrong live.
New sites get a short generated address (
zen-wreath-y76r.webly.site
); don't pass
unless the person asks for a specific one (up to 56 characters; a taken
one is a
, not a variant). On Free each site can change its webly.site
address once (
; Hobby and Pro unlimited), so run
first and rename only to the exact name the person asked for.
On Hobby and Pro the workspace also has a namespace
and each published site answers at
(
https://fall-out-boy.kev.webly.site
, the label from the site's name, unique only
within the namespace). Share
: the primary address (a custom domain
when one is live, else the vanity, else the flat address, unless the owner chose a
webly.site address as primary);
lists every
address the site answers at.
changes a site's label;
/
/
handle the namespace. Renames are scarce (Hobby 5, Pro 10, lifetime), so rename
only to the exact name the person asked for, and tell them old vanity addresses
stop working. The new addresses need about a minute for HTTPS: check
until
is
, then tell them they're live.
On
, give them
.
A team workspace has one owner (
→
). Ownership of the workspace
itself (not moving a website) changes only in the dashboard's People page, by the
owner; you can't do it, so send them there. The card and subscription stay with
the workspace.
New content, including blog posts and repeating content (products, team, FAQs),
goes in the site's source files; don't create collections or blog posts, the CMS
is deprecated. A site that already reads collections or a managed blog keeps
using those tools for that content until the owner asks to move it. Forms
post with
, never
, and never ask for card
numbers, passwords, ID numbers or health details (submissions are plain text).
If the owner wants an email per submission, turn it on with
(off by default). Emails go out on Hobby and Pro;
on Free the choice is saved: give the owner
. Name the email
field
so replying to an alert answers the visitor. Each workspace takes
1,000 submissions a month on Free (10,000 Hobby, 100,000 Pro); past that they're
held: hidden, no alerts, and deleted at the monthly reset unless the owner
upgrades. When
shows
, tell the owner and give them
.
Details are in llms.txt.
names the missing capability in
: the grant was
narrower than the task, so tell them which access level covers it.
/
: call a Webly tool again to re-trigger sign-in; don't start a
second attempt while one is waiting. Other people and agents may edit the
same site at once, and people may edit text, styles, layout,
sections, new elements and images, pages and brand colours, and component props in the dashboard, on static sites too (History shows them as Editor), so re-read a file before editing it. On a static site the editor's classes compile into
, linked from each page that uses them: keep that file and its
. Prefer
for small edits. Send
(the
your read returned) with
/
: their edits to other lines are merged with yours;
means you both changed the same lines — read the file
again, re-apply your change keeping theirs, resend with the new version.
shows what others wrote since a version. Publish with
set to the one the person previewed. History is linear, so the
versions between the last publish and that one go live with it (newer ones stay
unpublished); the response's
lists the ones other people or
agents wrote (who, app, message). Tell your person what of theirs went live.
Publishing an older version puts nothing new live, and
is empty.
To help someone choose a version:
and
(from the
version before it) show what it changed, and
gives a private link
to how it looked for an hour, changing nothing.
Git:
gives a read-only clone of a signed-in site's source and
history (one commit per version). Its token lasts one minute, so run its
(or
inside the clone) straight away as
WEBLY_GIT_TOKEN=<token> <clone>
, never with the token in the URL. Check
with
before asking again. Never
; write through the tools.
Turn a static site into a React site (or back)
Create a new site of the other kind and port the pages yourself: components,
and React state for what scripts did (or plain HTML and small scripts the
other way). Leave the original untouched until your person is happy with the
new one.
Duplicate or move a site
Hobby and Pro, in both workspaces (
otherwise: give the
person
).
copies a site 1:1: every
version, media, CMS, form submissions and settings, passwords; it is published
if the original is (
publish.status: "building"
means a bigger site is still
building and goes live by itself: tell your person it is still working), gets its own addresses, and custom domains stay with the
original.
moves a site into another workspace your person
admins, at once: everything comes along, including its webly.site address and
custom domains, except form email alerts: their recipients are cleared, so set
them again there (
). Its vanity address changes to the
new workspace's and links to the old one stop working, so confirm first and
share
.
lists the workspaces your person
admins and whether the site fits (
:
,
,
); ask which one. Both need a signed-in person (OAuth) to reach
another workspace. To give it to someone else, ask for their email and call
start_website_transfer { toEmail }
: they're emailed and it waits on their
Transfers page, where they accept or decline it (or their agent:
,
accept_website_transfer { transferId }
,
). There are no transfer codes.
Custom domains
Needs a signed-in account (MCP) on Hobby (5 domains) or Pro (25). On Free,
is
: give the owner
.
"Connect example.com to my site":
- Pick the site with . Never guess it from the hostname.
- For a bare domain, ask first:
- (recommended). It works with every DNS provider.
The person then forwards to it at their registrar, which is
free and takes a minute, but usually http-only (see below).
- directly. Only if their DNS provider supports CNAME
flattening or ALIAS at the root (Cloudflare, Namecheap, Porkbun…).
For a subdomain such as , just add it.
- Call , then . If it returns a , give the
person that link first: they sign in at their DNS provider (Cloudflare for
any hostname; GoDaddy and others for www once they support it) and approve,
and the records are set for them. They open it in the browser where they
use Webly. With Cloudflare () Webly also forwards the
bare domain of a www domain if they allow redirects on Cloudflare's screen
and nothing is served there yet (if isn't ok after
verifying, give it to them). If records of theirs are in the way, nothing
is replaced until they approve the exact changes shown after signing in;
approving switches the hostname at once, so for a site live today offer the
manual records (TXT first) to move without downtime. When you
and the response has , ask whether to delete the
records Webly added too, and if yes give them .
Otherwise (name.com, Squarespace, Google and most other providers), or as
the fallback, give every required entry exactly as
returned, as a Type / Name / Value table: the CNAME and the
TXT records. The TXT issues the HTTPS (SSL) certificate
and is always needed; without it HTTPS can take hours. If it isn't in
yet, call a few seconds later and give it then.
For a www domain, also give the forwarding rule (URL
forwarding at their registrar makes the bare domain work too, usually over
plain http only; for links, a provider with ALIAS can add the
bare domain as a second domain on the site: TXT records first, the ALIAS
once it's active). Check it with (,
), not in a browser: Chrome quietly retries a bare
domain with . Provider tips:
- Type only the Name shown (, or for the root). GoDaddy and
Namecheap add the domain themselves.
- On Cloudflare, set the record to "DNS only" (grey cloud).
- Moving a domain that is live elsewhere? Keep its current record and add
only the TXT records (the certificate ones and the optional ownership
one). Then:
- Poll until the domain is . That means ownership
is verified and the certificate is deployed. Step 2 isn't enough.
can't show this yet, because the old host still answers.
- Ask the person to switch the CNAME.
- Run
webly domain-watch <hostname>
to confirm traffic now reaches
Webly.
- Start watching in the background right away. Don't wait for the person to
say they're done:
webly domain-watch <hostname>
as a background task. It prints ,
and as each happens and exits once the domain is live.
Without a shell, call every .
Every domain response has with the step (1 DNS record, 2 HTTPS
certificate, 3 live) and what to do. Tell the person when each step
completes.
- Once live: confirm loads. The first domain to go live
on a site becomes its primary address by itself (), unless a
primary was already chosen (another domain, or a webly.site address picked
with ); every other address redirects to the primary.
If another domain is already primary, offer
to switch, or if they want a
webly.site address to be the primary (their custom domains then redirect
to it; say so). If it's
, relay , have them fix the record, then call
again. If the domain is active but their browser says the
server "could not be found" right after removing and re-adding it, their
DNS cached the gap: it clears within the zone's negative-cache time (30
minutes by default on Cloudflare), or sooner if they flush their DNS cache and
the stale answer was cached on their device (not by their router or ISP).
Adding a domain publishes nothing and takes nothing offline. The
address keeps working.
Rules
- The token is a secret that proves ownership. Never print it, log it, commit
it, or put it in a URL other than through .
- Only state URLs, sites and counts that a command or tool actually returned.
- Don't set up MCP for someone who only wants a quick link; offer it when they
want to keep or grow the site.
- One anonymous site per machine. If they want a second site kept, claim the
first, then create the second over MCP and it.
- A folder belongs to the site in its . Never deploy it
to, or claim, a different site unless the person asks.