Change content without changing how your site works.

Open a terminal in the directory that contains the website HTML files.

$ cd /path/to/static-output
$ npx xyle init .
$ npx xyle dev .

The first command shows an editor key. Store this key in a secure password manager.

The second command shows two addresses. Open the address that ends in /edit.

1. Enter the editor key.
2. Select visible text, a link, an image, or a supported section.
3. Make the change with the controls beside the selected content.
4. Open Changes to examine the old and new values.
5. Use Revert to remove one change. Use Discard to remove the complete draft.
6. Select Publish after the review is complete.

Xyle patches only the reviewed ranges. It keeps unrelated source bytes unchanged.

Uploaded images become content-addressed static files. Xyle does not put website content in a separate database.

For a generated site, coordinate with the developer before another framework build. A new build can replace edits in final output.

After publication, reload the public address and examine the result.

A compatible browser agent can inspect editable content and prepare changes from a natural-language request.

The agent uses the same safety rules and ChangeSet as the visual editor. It cannot publish.

Review agent changes in the Changes drawer before you select Publish.

Create a scoped API token with Cloudflare Pages: Edit access. Store it in the CLOUDFLARE_API_TOKEN environment variable. Do not add the token to the website directory.

$ cd /path/to/static-output
$ npx xyle cloudflare . \
    --project=my-static-site \
    --account-id=YOUR_ACCOUNT_ID

Xyle creates or validates a Direct Upload project, stores encrypted owner credentials, deploys the complete site, and prints its secure /edit URL.

Git-integrated Pages projects are not supported. For an existing Direct Upload project, Xyle requires a matching managed snapshot or an explicit --force adoption.