Yes. You can import a copy of your WordPress site into Tracy and ask for changes in plain language instead of clicking through wp-admin. Tracy edits that copy, not your original host, and supported changes are recorded in Site changes, with a Diff where one is available.
How do I edit my WordPress site with AI?
The route is import, connect, then type. Import a site covers every import message in detail.
- Open Add site, then Import existing site. Choose WordPress and enter the address of the site you already run.
- Connect the original site in one of two ways: give Tracy admin access with your normal WordPress admin username and password, not an application password, or choose I will install it myself, install Claude Cowork on the site yourself and paste the token from Settings > Claude Cowork.
- Wait for the copy. Tracy restores the hosted copy, starts its agent and returns the copy’s own address. You work on that copy from then on.
- Type your requests the way you would write them to a colleague.
These are the requests the Tracy for WordPress page gives as examples:
- “Put our opening hours in the footer.”
- “On mobile, stack the three service boxes.”
- “Add a Contact page with our address and a map link.”
- “Change the phone number everywhere it appears.”
Tracy reads the site before it changes anything, so the answer is about your site, not a generic WordPress example.
Do I need to open wp-admin?
No, not for everyday changes. You describe the change in the chat and Tracy makes it on the copy, so you do not have to sign in to wp-admin to edit a page, a menu or a phone number.
Open admin is still there. In Site settings, Open admin opens the website’s administration, and supported edits you make there appear in Site changes with the source CMS admin, where By shows the admin user who made them. Those admin edits are listed without a before and after.
What happens to my original site?
Import creates a separate copy for editing, and the original keeps serving visitors. Import does not redirect the original site’s DNS, and it does not replace its content or design.
Connector setup can change the original site. Automatic setup can install, update or activate the Claude Cowork connector on the original WordPress site before copying its files and content, and for a manual install you do that yourself. The connector is Tracy’s CMS integration, separate from Anthropic’s Cowork product.
After the import, Tracy edits the copy and does not send its edits back to the original host. Publishing changes the state of the copy hosted by Tracy; it does not send your edits back either. Treat publishing the copy and directing visitors to it as separate tasks, and read Publish and go live and Domains, DNS and HTTPS before you change where visitors arrive.
How do I see what changed and undo it?
Site changes lists every recorded change, newest first, with a description, the time, the type and who made it. Open a row from the chat to see the files Tracy changed and the content Tracy wrote; on WordPress, each available file opens in a Diff that shows the exact lines that moved. See what Tracy changed explains the columns and the sources.
To undo one request, select Undo this request in the row, or use Undo file changes where it is offered, and confirm. Undo puts back only eligible files that the change touched, later changes to those files can block it, and database content is not restored. For a text change, choose Ask Tracy to revert and Tracy receives the request in the chat you have open on that site.
For many changes at once, restore a backup: the Initial backup is made when the site is set up, and you create more in Site changes with Create a backup. Restore everything returns files and database to that point and deletes everything saved after it, and only an Owner or Editor can do it. Undo and backups lists what each option does and what it cannot bring back.
Not every change can be undone. AI can make mistakes, so check the page itself after a change rather than treating Tracy’s reply as proof that it worked.
When is this not the right approach?
Imported copies and chat edits suit everyday changes to a running WordPress site. This is not the right approach when:
- Your site is not on WordPress or Joomla. Shopify and custom-coded applications are not supported, and EmDash, Shopify and hand-coded sites cannot be imported.
- You need a drag-and-drop builder. Tracy has no drag-and-drop canvas: you describe the change and the site’s own theme carries it.
- Your setup is unusual. Platform support does not guarantee compatibility with every hosting setup, theme or plugin.
- You need every change to wait for approval. Ordinary edits can apply immediately; Tracy has targeted confirmations for consequential actions, not a universal approval step.
- You need a guaranteed undo. Not every change can be undone, later conflicting edits can prevent an earlier change from being undone, and external effects cannot be recalled.
Frequently asked questions
Can I edit my WordPress site with AI without using wp-admin?Yes. Import a copy of the site into Tracy, then ask for changes in the chat. Open admin stays available for the edits you prefer to make there.
Does Tracy change my original WordPress site?Import creates a separate copy for editing and the original keeps serving visitors, but connector setup can install, update or activate Claude Cowork on the original site. Edits made in Tracy are not sent back to the original host.
Do I need to install anything on my WordPress site first?With admin access, Tracy can install, update or activate the Claude Cowork connector when the account is an Administrator permitted to install plugins. If you install it yourself, paste its token from Settings > Claude Cowork.
How do I undo a change Tracy made?In Site changes, select Undo this request, or Ask Tracy to revert for content, and confirm. Later edits can block an undo, and not every change can be undone, so a backup is the answer for many changes at once.
Can I still use the WordPress admin?Yes. Open admin opens the site’s administration, and supported edits made there are listed in Site changes with the source CMS admin.