Skip to content

v0.2.0 — the admin console

Choose a tag to compare

@Mrshahidali420 Mrshahidali420 released this 16 Aug 15:17
· 130 commits to d296cb254936936ec6f18d5efe340924637a9201 since this release

Connecting a client used to mean reading the README, finding the REST route, minting an Application Password from your WordPress profile, and assembling the config by hand. This release replaces that with a screen.

Install: download sitehelm-0.2.0.zip below → Plugins → Add New → Upload PluginActivate → open SiteHelm → Connect.

Four screens, one menu

Connect — the MCP endpoint, an Application Password created in place and shown exactly once, and a ready-to-paste configuration for Claude Code, Cursor, or any other MCP client. It says "Ready to connect" until a client has actually called, warns when the site is not on HTTPS, and when Application Passwords are disabled it explains why rather than offering a button that cannot work.

Activity — every operation a client has performed, newest first, with target, outcome, actor and rollback reference. Filterable by operation or correlation id. It states a rollback reference rather than offering an undo button, so a rollback stays a deliberate act performed through the gateway.

Status — which modules are active, inactive or version-blocked, the detected version of each integration, whether the ledger tables exist, and the environment SiteHelm is running in. Storage being unavailable overrides the module verdict, because nothing can be recorded without it.

Operations — the full catalogue of what a connected client can ask this site to do, grouped by tool, each marked read or write and badged when it requires preview, is destructive, or is high risk.

The console is read-only apart from the single button that mints a credential. No options screen, no dashboard widget, no cron jobs.

Unchanged

The gateway, the 51 operations, the two-phase write pipeline, snapshots, verification, the change ledger and rollback are all exactly as they were in 0.1.0. This release adds a way to reach them; it changes nothing about how they behave.

Requires WordPress 6.6+ and PHP 8.1+. Always connect over HTTPS — an Application Password sent over plain HTTP is a credential sent in the clear.

Full detail in CHANGELOG.md.