WordPress
WordPress CLI changelog
Read WordPress CLI release notes, including new capabilities, changes and fixes.
Notable changes to @wirecat/wordpress-cli. One section per version, newest first.
0.1.1 — 19.11.2026
Fixed
posts delete --dry-runnamesapi.posts-deletetoo. The delete sends through theapigroup's delete, whose own key the run checks. Withposts.deleteset toallow, the preview saidallowwhile the run still asked.- The agent skill's header is valid YAML again.
skills/wordpress-cli/SKILL.mdhadsite: postsin its unquoteddescription, which a YAML reader takes as a new key and refuses. Agents and wirecat.dev that read the skill's header now can.
0.1.0 — 19.11.2026
Added
- Started from
@wirecat/cli-template0.32.0. - Built from one file,
wirecat.config.ts, with no hooks, plus one command name and the permission key form inscripts/generate.ts. wordpress <profile> session start --site <address> --login <user>signs in with an application password from stdin, checked againstGET /wp/v2/users/me, and keeps it with its site. It goes to that site alone.wordpress <profile> synccopies your posts and pages into WireCat's local store, every status and the trash too, with their tags, categories and authors. The text is kept as Markdown. Later syncs read only what changed.wordpress <profile> posts list|show|search|stats,tags list,users listandchannels listread the copy, offline too.wordpress <profile> posts create|update|publish|unpublish|deletewrite to the site. A new post is a draft. Publishing, now or with--at-time, has its own key. A delete goes to the trash, and--allow-deletedeletes for good. Each asks by default. A post with blocks or embeds that Markdown cannot keep keeps its body unless--replace-body, and a post changed on the site since the last sync is not overwritten. Pages are read, not written: a write to a page stops withcontent.write-unsupported.wordpress <profile> apiruns everywp/v2route of WordPress 6.9.4, each with its own flags, help and--json. Publishing and deleting for good need their own keys. Installing a plugin, changing a site setting, making or changing a user or a comment, and changing templates, widgets, menus or navigation ask by default.api posts-createandapi pages-createcheckposts.createtoo, and their updates checkposts.update.batch/v1and making an application password are never offered.