Jordy Meow

<p><strong>Chagency</strong> is the first chatbot to ship directly on top of the new AI Client introduced in WordPress 7.0 — <code>wp_ai_client_prompt()</code>, Connectors, and the Abilities API. Every prompt flows through WordPress core, every provider is a Connector you already configured under <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Connectors</strong>, and every action it exposes is a registered Ability that other plugins (and other AI agents) can call.</p>
<p>There is no other plugin on wordpress.org that builds on <code>wp_ai_client_prompt()</code> today. Chagency is the reference case: a small, native chatbot that proves the framework works, ships zero vendor SDKs, and grows alongside the Abilities API into a real agent.</p>
<p>It runs in the WordPress admin and, when you turn it on, on every page of your public site. The name (chat + ai + ency) is meant as a small bridge between the new AI primitives shipped with WordPress and the broader world of chat and agents. It starts as a chatbot today and turns into an agent tomorrow, without a rename.</p>
<h3>🪨 Built on WordPress, period</h3>
<p>Chagency relies entirely on what WordPress 7 ships in core:</p>
<ul>
<li><code>wp_ai_client_prompt()</code>, the AI Client API.</li>
<li><code>wp_get_connectors()</code>, the Connectors API.</li>
<li><code>wp_register_ability()</code> / <code>wp_get_ability()</code>, the Abilities API.</li>
<li><code>@wordpress/components</code>, <code>@wordpress/element</code>, <code>@wordpress/boot</code>, the Gutenberg toolkit.</li>
</ul>
<p>That is the entire dependency surface. <strong>No bundled AI vendor SDKs, no third-party JavaScript libraries beyond the Gutenberg stack, no telemetry, no phone-home.</strong> The plugin stays small on purpose: fewer moving parts means less friction, fewer security holes, less to break when WordPress, browsers, or providers change.</p>
<p>You will need at least one AI provider plugin (e.g. <em>AI Provider for Anthropic</em>, <em>AI Provider for Google</em>, <em>AI Provider for OpenAI</em>) to talk to a model. That is WordPress 7’s architecture: providers are separate plugins that register a Connector. They are not a Chagency dependency.</p>
<p>💡 <strong>Tip:</strong> For the smoothest setup, install <a href="https://wordpress.org/plugins/ai-engine/" rel="ugc">AI Engine</a>. It registers every AI provider it manages as a Connector, so a single configuration covers all your WordPress 7 AI plugins (including Chagency). Every request then flows through one clean, unified system.</p>
<h3>🪄 What you get</h3>
<ul>
<li>A floating chat panel pinned to the bottom-right of every page (admin and / or public site, controlled by two independent toggles).</li>
<li>A single settings page under <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Chagency</strong>, with the bare minimum: where to show the chatbot, the chat title, the greeting, the system instruction, and the model preference.</li>
<li>Live updates: flipping a toggle in Settings shows or hides the launcher immediately on the same page, no reload needed.</li>
<li>Per-provider <strong>Test</strong> buttons that fire a canary prompt and report round-trip time.</li>
<li>Conversation persistence in your browser’s localStorage, scoped per user.</li>
<li>Placeholder expansion (<code>{user_name}</code>, <code>{site_name}</code>, <code>{current_page}</code>, <code>{current_url}</code>, <code>{user_role}</code>, <code>{site_url}</code>) so the assistant always knows who and where it is.</li>
<li>Exposed as an Ability (<code>chagency/send-message</code>) so other plugins, MCP clients, and AI agents can invoke Chagency directly.</li>
</ul>
<h3>🚀 Getting started</h3>
<ol>
<li>Install and activate <strong>Chagency</strong>.</li>
<li>Install and configure at least one AI provider plugin under <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Connectors</strong> (we recommend <a href="https://wordpress.org/plugins/ai-engine/" rel="ugc">AI Engine</a>, which exposes all its providers as Connectors at once).</li>
<li>Click the chat launcher in the bottom-right of any admin page and start talking.</li>
<li>Want it on the public site too? Open <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Chagency</strong> and flip the second toggle.</li>
</ol>
<h3>🙋 Frequently Asked Questions</h3>
<h4>Why “Chagency”?</h4>
<p>It’s a portmanteau of <em>chat</em>, <em>AI</em>, and a bit of <em>agent</em>. Not “agency” in the sense of a marketing shop. The plugin starts as a minimal chatbot for the new WordPress 7 AI framework and grows alongside the Abilities API into a true agent.</p>
<h4>Does it need WordPress 7?</h4>
<p>Yes. It uses <code>wp_ai_client_prompt()</code>, <code>wp_get_connectors()</code>, and the Abilities API, all added in WordPress 7.0. On older versions it refuses to boot and tells you why.</p>
<h4>Which AI providers are supported?</h4>
<p>Whatever you configure under <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Connectors</strong>. Chagency is provider-agnostic. Anthropic, Google, OpenAI, or any third-party Connector are treated equally.</p>
<h4>Can visitors on the front end use it?</h4>
<p>Yes. Open <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Chagency</strong> and turn on <em>Show on the public site</em>. The chat then appears for every visitor, signed in or not.</p>
<h4>Does it store my conversations?</h4>
<p>No. Conversations live only in your own browser (localStorage, per user). Hit <em>Reset</em> in the panel to clear them. Nothing is stored server-side.</p>
<h4>Can I use it as a building block in my own plugin?</h4>
<p>Yes. The <code>chagency/send-message</code> Ability is registered on <code>wp_abilities_api_init</code> and can be called with <code>wp_get_ability( 'chagency/send-message' )->execute( array( 'message' => '...' ) )</code>.</p>
<h3>Source code</h3>
<p>The unminified React / JavaScript source is shipped inside the plugin folder under <code>src/</code>, alongside the compiled output in <code>build/</code>. Public source repository: https://github.com/jordymeow/chagency</p>
<p>To rebuild from source:</p>
<pre><code>pnpm install && pnpm run build
</code></pre>
<p>The build is <code>@wordpress/scripts</code> (webpack) with no custom plugins or transforms.</p>


Chagency


Nobody cares. Or maybe some do. I do! 😼 The first and only chatbot (as of today) to use the AI Client that ships with WordPress (from v7). This chatbot is perfect for testing the AI Client and the AI providers built for it.


The 1st and only chatbot to use the AI Client

The first chatbot built natively on the WordPress 7 AI Client. No bundled SDKs, no third-party JavaScript, no telemetry.

miya

<p>Kagivault is an encrypted vault for the <strong>WordPress 7.0 AI Connectors API</strong>. Out of the box, WordPress stores the API keys you configure on <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Connectors</strong> (OpenAI, Anthropic, Google, OpenRouter, and any other AI provider registered with the AI Client) as plaintext rows in the <code>wp_options</code> table. Anyone with database access — backups, leaked dumps, host migration files — can read them.</p>
<p>Kagivault wraps each AI Connectors key with <strong>XChaCha20-Poly1305 (authenticated encryption)</strong> and protects the data-encryption key with a <strong>vault password derived through Argon2id</strong>. The vault password is never persisted, and the vault automatically re-locks after a short, configurable idle timeout. Unlock from the admin UI, and the WordPress AI client transparently sees the decrypted keys — no other plugin changes required.</p>
<h4>Highlights</h4>
<ul>
<li>Drop-in encryption for every AI Connectors provider (<code>connectors_ai_*_api_key</code> rows)</li>
<li>Vault password unlock with idle-timeout auto-lock</li>
<li>Recovery key as a parallel unlock path</li>
<li>Optional: link a WordPress login password so signing in automatically unlocks the vault</li>
<li>Easy-mode initialization — no separate vault password to remember if you just want one-click setup</li>
<li>Transparent for the core WP AI client and the Connectors admin page</li>
<li>Versioned blob format for future cipher upgrades</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>WordPress 7.0 or newer (uses the Connectors API introduced in 7.0)</li>
<li>PHP 8.3 or newer</li>
<li>PHP sodium extension with <strong>XChaCha20-Poly1305 AEAD</strong> (<code>sodium_crypto_aead_xchacha20poly1305_ietf_encrypt</code>)</li>
<li>PHP sodium extension with <strong>Argon2id</strong> (<code>SODIUM_CRYPTO_PWHASH_ALG_ARGON2ID13</code>, requires libsodium 1.0.13+)</li>
</ul>
<p>The bundled sodium extension shipped with PHP 8.3+ on most platforms (Debian/Ubuntu <code>php-sodium</code>, RHEL <code>php-sodium</code>, Alpine <code>php-sodium</code>, Windows official builds) includes both capabilities. The plugin refuses to activate and surfaces a clear admin notice if either is unavailable.</p>
<h3>Privacy Policy</h3>
<p>Kagivault does NOT:</p>
<ul>
<li>Send any data to external servers</li>
<li>Track users</li>
<li>Use cookies for tracking</li>
<li>Share data with third parties</li>
</ul>
<p>Kagivault DOES:</p>
<ul>
<li>Process and store encrypted API keys locally on your server (<code>wp_options</code>)</li>
<li>Keep the data-encryption key only in a short-lived transient that expires after the configured idle timeout</li>
</ul>
<h3>Support</h3>
<p>For support, bug reports, or feature requests:</p>
<ul>
<li>Website: https://github.com/benridane/kagivault</li>
</ul>
<h3>Development</h3>
<p>Development happens on GitHub. Pull requests welcome!</p>
<ul>
<li>Follow WordPress coding standards</li>
<li>All code must pass <code>wp plugin check kagivault</code></li>
</ul>


Kagivault

Encrypts WordPress AI Connectors API keys (OpenAI, Anthropic, Google, OpenRouter) at rest with XChaCha20-Poly1305 + Argon2id.

Chagency vs Kagivault