v1.2.2

Release Haydi 1.2.2

Security release: enforce the code-editor access floor and live token issuer checks, require browser approval for URL fetches, show authoritative file approval targets, and fail closed on unpinned HTTP transports.

Haydi 1.2.1

Security release.

• The REST and MCP API (/wp-json/haydi/v1/*) now requires a valid Bearer token on every request; the fallback to logged-in-user capability checks has been removed. Provision a token from the Haydi settings page to use the API.
• Haydi's admin page, audit log, and chat access default back to Administrators only (manage_options). Sites that want to grant access to other roles can use the haydi_access_capability filter; the Editor model restriction setting is preserved.

Haydi 1.2.0

Haydi 1.2.0 makes multi-step AI actions more reliable and adds controlled Editor access to the WordPress admin experience.

Highlights

• More reliable follow-up: after you review and apply a change proposed by Haydi, the AI can now continue where it left off instead of losing context.
• Editor access: trusted Editors can now use Haydi alongside Administrators by default.
• Administrator model controls: Administrators can choose which model Editors use under Settings → Haydi, while retaining full model selection themselves.
• Flexible access rules: developers can change who has access through the haydi_access_capability filter.

Upgrade note

Browser access previously required manage_options; version 1.2.0 admits trusted Editors by default. Sites that want to preserve administrator-only access can add:

add_filter( 'haydi_access_capability', static fn() => 'manage_options' );

Bearer-token REST and MCP authorization remains independent of WordPress roles.

Haydi 1.1.0

Haydi 1.1.0 makes the full site-management toolset part of one plugin and improves consistency across chat, MCP, OpenAI, Anthropic, and Google.

Highlights

• Complete built-in toolset: file writes and edits, SQL queries, and PHP execution no longer require separate extension files.
• One Tool Catalog: chat and MCP share canonical schemas, aliases, approval policy, and implementations.
• One approval pipeline: every browser mutation uses the same authenticated execution path and approval card.
• Structured results: native JSON-compatible results stay structured until an adapter requires text, avoiding provider double-encoding.
• Updated local test connectors for Anthropic 1.0.3, Google 1.1.0, and OpenAI 1.0.3.

Upgrade note

The separate haydi-full-extensions.zip package is retired because all supported tools are now built into haydi.zip. Custom integrations should register through the haydi_register_tools action; legacy additive chat and MCP filter hooks remain supported.

Haydi 1.0.1

Release 1.0.1

Haydi 1.0.0

Release 1.0.0