Ibrahim

Tessera is a developer library for plugin authors who register abilities via <code>wp_register_ability()</code> and want snapshot capture, audit logging, approval workflows, and one-click rollback for every invocation across REST, MCP, internal PHP, and WP-CLI without building it themselves.
Declare what state your ability touches; Tessera handles the safety wrapper.
<h4>What you get out of the box</h4>
<ul>
<li>Pre + post snapshots. Every safety-enabled invocation captures declared state before the callback and (on success) after, so the audit log can show a real diff.</li>
<li>Audit log. One row per invocation with ability name, caller (REST/MCP/CLI/internal), user, args, result, status, duration, pre/post hashes, and parent_invocation_id for nested calls.</li>
<li>One-click rollback. Restore captured state from post_meta, options, taxonomy term assignments, user roles + caps. File contents support tiered drift detection (mtime / mtime_size / critical_hash / full_hash) plus opt-in real byte-level rollback via <code>full_content</code> strategy.</li>
<li>Drift check on rollback. Live state is hashed and compared to the snapshot’s post-state before restoring; if they differ the rollback returns an error unless forced.</li>
<li>Concurrency lock. Capture + execute is serialised per surface set via a MySQL advisory lock so two simultaneous invocations do not capture each other’s mid-states.</li>
<li>Encrypted redaction. Scrub secrets out of args, results, and snapshots. Stores redacted values as AES-256-GCM envelopes so rollback can still restore them.</li>
<li>Approval queue. When <code>safety.requires_approval</code> is set, the wrapper blocks execution and returns a 202 pending response. A human approves or rejects via wp-admin, WP-CLI, or REST. Multi-stage sequential or parallel approval chains are supported.</li>
<li>Multisite support. Each subsite gets its own set of <code>wp_<N>_abilityguard_*</code> tables, with auto-install on <code>wp_initialize_site</code> and auto-drop on <code>wpmu_drop_tables</code>.</li>
<li>Retention. Daily WP-Cron prunes old log rows (defaults: 30 days normal, 180 days destructive) and orphaned snapshots.</li>
</ul>
<h4>Surfaces</h4>
<ul>
<li>PHP API with <code>wp_register_ability( $name, [ ..., 'safety' => [...] ] )</code> and helpers <code>abilityguard_rollback</code>, <code>abilityguard_snapshot_meta</code>, <code>abilityguard_snapshot_options</code>.</li>
<li>REST: <code>/abilityguard/v1/log</code>, <code>/log/<id></code>, <code>/log/export</code>, <code>/rollback/<id></code>, <code>/rollback/bulk</code>, <code>/approval</code>, <code>/approval/<id>/approve</code>, <code>/approval/<id>/reject</code>, <code>/approval/bulk</code>, <code>/approval/export</code>, <code>/retention</code>, <code>/retention/prune</code>, <code>/health</code>.</li>
<li>WP-CLI: <code>wp abilityguard log list/show</code>, <code>wp abilityguard rollback <id></code>, <code>wp abilityguard approval list/approve/reject <id></code>, <code>wp abilityguard prune</code>.</li>
<li>wp-admin: Tools > Tessera. Hybrid timeline + command-palette search, snapshot drawer, JSON-highlighted Input/Result tabs, invocation chain navigation, and real rollback against the captured snapshot.</li>
</ul>
<h4>Example</h4>
<pre><code>wp_register_ability( 'my-plugin/update-product-price', array(
 'label' => 'Update product price',
 'description' => 'Updates the price on a WooCommerce product.',
 'category' => 'woocommerce',
 'input_schema' => array( /* ... */ ),
 'permission_callback' => fn() => current_user_can( 'manage_woocommerce' ),
 'execute_callback' => fn( $args ) => update_post_meta( $args['product_id'], '_price', $args['price'] ),
 'safety' => array(
 'destructive' => true,
 'requires_approval' => false,
 'snapshot' => fn( $input ) => array(
 'post_meta' => array( $input['product_id'] => array( '_price', '_regular_price' ) ),
 'options' => array( 'woocommerce_last_price_change' ),
 ),
 ),
) );
</code></pre>
<h4>Documentation</h4>
Full plugin-author documentation lives at the GitHub repo: https://github.com/ibrahimhajjaj/abilityguard
<h3>Source Code</h3>
The full source for Tessera, including the unminified React source for the admin app, lives on GitHub: https://github.com/ibrahimhajjaj/abilityguard
<ul>
<li>The admin bundle <code>assets/admin.js</code> is compiled from <code>assets/admin.jsx</code> (React + JSX, no preprocessor magic beyond JSX).</li>
<li>The bundler is <a href="https://esbuild.github.io/" rel="nofollow ugc">esbuild</a>, configured in <code>scripts/build.mjs</code>.</li>
<li>To rebuild the admin bundle from a fresh checkout, run <code>npm install</code> once, then <code>npm run build</code> whenever <code>assets/admin.jsx</code> changes. This regenerates <code>assets/admin.js</code> in place.</li>
<li>The release zip published to the WordPress.org directory is produced by <code>scripts/build-release.sh</code>, which excludes development artifacts (tests, examples, build configs) but keeps everything required for the plugin to run.</li>
</ul>

Tessera for the Abilities API

Snapshot, audit, and rollback layer for plugins that register abilities via the WordPress Abilities API.

Timon

SlyTranslate wires AI translation into WordPress at three different levels: the admin UI, the Gutenberg editor, and from external LLM tools via MCP. Whichever level you work at, the same language plugin integrations and translation quality controls apply.
It works with any LLM available through a WordPress AI connector and natively supports Polylang, WP Multilang, WPGlobus, and TranslatePress Multilingual.
What it does
<ul>
<li>Translates posts, pages, and custom post types into any language managed by your active language plugin</li>
<li>Translates selected text or entire Gutenberg blocks inline, without leaving the editor</li>
<li>Exposes the same functionality as MCP abilities, so external LLM tools (Claude Code, Codex, and others) can drive translations programmatically</li>
<li>Carries SEO metadata (title, description) through the same translation workflow as the post content</li>
<li>Handles long and structured content with chunking and output validation</li>
<li>Supports model-specific profiles that tune prompt style and retry behavior for known model families</li>
</ul>
<h4>Workflow 1 — Admin UI translation (posts & pages overview, side panel)</h4>
Translate full posts or pages directly inside WordPress admin — either one at a time from the editor side panel or in bulk from the list view.
Requirements: language plugin + configured AI Connector
From the post/page list, select one or more items and choose a translation action from the bulk-actions menu. A dialog lets you pick target language, model, and whether to overwrite existing translations. Progress updates live while the translation runs, and you can cancel at any time.
From the editor side panel, the same controls appear alongside the post you are currently editing. TranslatePress users get an equivalent panel inside the TranslatePress visual editor on <code>?trp-edit-translation</code> pages.
The language plugin (Polylang, WP Multilang, WPGlobus, or TranslatePress) handles the translated post as it normally would — SlyTranslate creates or updates the translated entry and lets the language plugin own the relationship.
<h4>Workflow 2 — Inline Gutenberg translation (block or selected text)</h4>
Translate content while writing, without touching a language plugin or a full-post workflow.
Requirements: configured AI Connector
Select any text in a Gutenberg block and the block toolbar gains a Translate button. The selected text is replaced with the translation in place. When no text is selected, the button translates the entire block.
This workflow is self-contained: it does not require a language plugin and does not create or modify translated post entries. It is useful for one-off corrections, translating imported content on the fly, or working in a single-language site where you just need AI rewriting in another language.
<h4>Workflow 3 — LLM wrapper via MCP (Claude Code, Codex, and others)</h4>
Drive WordPress translations from inside your LLM tool of choice.
Requirements: language plugin + WordPress application password (token) + WordPress MCP Adapter plugin
When a WordPress MCP Adapter is active, SlyTranslate registers its abilities over MCP. Any MCP-capable LLM client — Claude Code, Codex, custom agents — can then discover and call them.
In this workflow the LLM wrapper provides the translation itself. SlyTranslate’s MCP abilities handle the WordPress side: reading content structure, checking translation status, writing translated entries, and coordinating with the language plugin. No WordPress AI Connector is needed because translation is performed by the external model, not by WordPress.
A typical agent session:
<ol>
<li>Call <code>ai-translate/get-languages</code> to find valid target language codes.</li>
<li>Call <code>ai-translate/get-translation-status</code> on the source post to read <code>source_language</code> and <code>single_entry_mode</code>.</li>
<li>Translate the content using the agent’s own LLM.</li>
<li>Call <code>ai-translate/translate-content</code> to write the translated entry.</li>
</ol>
This is the right workflow for automating bulk site migrations, integrating translation into a CI/CD pipeline, or building a custom translation agent that uses a model not available as a WordPress AI connector.
<h4>Internal flow</h4>
<pre><code>┌──────────────────┐ ┌───────────────────┐ ┌────────────────────────┐
│ Admin UI │ │ Gutenberg │ │ LLM Wrapper │
│ (panel / list) │ │ (block / toolbar) │ │ (Claude Code, Codex…) │
└────────┬─────────┘ └────────┬──────────┘ └──────────┬─────────────┘
 │ REST │ REST │ MCP
 └──────────────────────┴──────────────────────────┘
 │
 ┌──────────▼──────────────┐
 │ SlyTranslate Ability │
 │ (REST / MCP endpoint) │
 └──────────┬──────────────┘
 │
 ┌───────────▼───────────┐
 │ AI Connector │ ← UI/block workflows
 │ (wp_ai_client_prompt)│ only
 └───────────┬───────────┘
 │
 ┌───────────▼───────────┐
 │ LLM (any provider) │
 └───────────┬───────────┘
 │
 ┌───────────▼───────────┐
 │ Chunk + Validate │
 └───────────┬───────────┘
 │
 ┌───────────▼───────────┐
 │ Language Plugin │
 │ Polylang / TP / … │
 └───────────┬───────────┘
 │
 ┌───────────▼───────────┐
 │ WordPress Post │
 └───────────────────────┘
</code></pre>
In the MCP workflow the LLM Wrapper acts as the translation engine — the AI Connector and LLM steps inside WordPress are bypassed.
<h4>Abilities reference</h4>
<pre><code>ai-translate/get-languages — List languages exposed by the active language plugin

ai-translate/get-translation-status — Show translation status for a content item, including `source_language` and `single_entry_mode`

ai-translate/set-post-language — Change the language assignment of an existing content item (Polylang only)

ai-translate/get-untranslated — Find content still missing a target translation

ai-translate/translate-text — Translate arbitrary text

ai-translate/translate-blocks — Translate serialized Gutenberg blocks

ai-translate/translate-content — Create or update one translated post/page/CPT entry

ai-translate/translate-content-bulk — Bulk-translate multiple entries

ai-translate/get-progress — Return live progress for a running translation

ai-translate/cancel-translation — Cancel a running translation

ai-translate/get-available-models — List models from configured connectors

ai-translate/save-additional-prompt — Save per-user additional instructions

ai-translate/configure — Read or update persistent plugin settings
</code></pre>
MCP call sequence
For reliable results in agent workflows:
<ul>
<li>Call <code>get-languages</code> first when the correct target language code is unknown.</li>
<li>Call <code>get-translation-status</code> before <code>translate-content</code> to read <code>source_language</code>, <code>single_entry_mode</code>, and whether a translation already exists.</li>
<li>Omit <code>source_language</code> unless you intentionally pin a source variant.</li>
<li>Set <code>overwrite=true</code> only when status or prior context confirms a target-language entry already exists.</li>
<li><code>translated_post_id</code> equals <code>source_post_id</code> in single-entry adapters (WP Multilang, WPGlobus, TranslatePress). In multi-post adapters (Polylang) the translated item has a sibling post ID.</li>
</ul>
<h4>Supported plugins</h4>
Language plugins
<ul>
<li>Polylang</li>
<li>WP Multilang</li>
<li>WPGlobus</li>
<li>TranslatePress Multilingual</li>
</ul>
SEO plugins (metadata translated alongside content)
<ul>
<li>Genesis SEO</li>
<li>Yoast SEO</li>
<li>Rank Math</li>
<li>All in One SEO</li>
<li>The SEO Framework</li>
<li>SEOpress</li>
<li>Slim SEO</li>
</ul>
<h4>Supported model profiles</h4>
Any LLM available through a WordPress AI connector works without configuration. The following model families have dedicated built-in profiles that tune prompt style, chunking, and retry behavior:
<ul>
<li>TranslateGemma — dedicated runtime with <code>chat_template_kwargs</code> support via <code>direct_api_url</code></li>
<li>TowerInstruct / Salamandra — bilingual framing, conservative chunking, stricter retries</li>
<li>Nvidia Nemotron — system-prompt-aware, reasoning-disable, provider-parameter forwarding</li>
<li>Qwen 3.x / GLM-4.6v / Gemma 4 / Phi-4 — thinking-aware profiles</li>
<li>EuroLLM / Llama 3.1-8B / SauerkrautLM — conservative chunking tuned for European languages</li>
<li>Ministral-3 / Ministral-8B — optimized for the Ministral model family</li>
</ul>
Additional profiles can be registered via the <code>slytranslate_model_profiles</code> filter.

SlyTranslate – AI Translation Abilities

AI translation for WordPress — admin UI, Gutenberg inline, and MCP workflows for external LLM tools.

Tessera for the Abilities API vs SlyTranslate – AI Translation Abilities