Link your first site

An application password, not your login. Then turn on only the abilities you mean.

1. Create an application password

In WordPress, go to Users → Profile and scroll to Application Passwords. Give it a name you will recognise later and create it. WordPress shows the password once.

2. Add the site in the app

Give the app the site URL and paste the application password. It is encrypted with Windows DPAPI before it touches the disk.

The app then checks that it can reach the site, that the plugin is installed, and what the site runs: Elementor, WPBakery, the block editor, WooCommerce.

3. Turn on what you actually want

Every ability is off. A freshly linked site can read nothing and write nothing until you say so, and the switches are per site, so a client site and your own can have completely different answers.

Start narrow. Reading pages and editing drafts is enough to see whether the thing works at all; publishing and file writes can wait until you trust it.

The app tells the agent exactly which abilities are on, so it does not spend a conversation trying things that will be refused.

Identities, if more than one person works here

Each identity is one WordPress user and one application password of its own. That means the site's own activity log attributes a change to the person it belongs to, rather than to a single shared robot account, which matters the first time a client asks who changed something.

Reference sites

A site can be marked as a source you only read from. That refusal lives in the transport, not in each handler. One rule with no gaps, rather than a check that has to be remembered in sixty places.

Useful for a site you are copying a design from, or a production site you want the agent to be able to look at and never touch.

Unlinking

Unlink a site and it disappears from the agent entirely. Not blocked. Invisible. The agent is not told there is a site it may not use, because that is itself information about a client.