Npcink

Npcink AI Client Adapter gives OpenClaw-compatible and similar AI clients one WordPress REST namespace for reading Npcink Governance Core capability guidance, routing approved read abilities through the WordPress Abilities API, and forwarding governed write requests to Npcink Governance Core proposal and commit-preflight endpoints.
Adapter is intentionally thin. It does not define abilities, store approval truth, run workflow queues, or execute final write mutations without Core approval and commit-preflight.
Adapter can be distributed as the Npcink AI suite entry plugin while Core and Toolkit remain separate plugins. Adapter health reports missing dependencies and dependency-sensitive routes fail closed with a structured missing dependency error.
Adapter exposes a machine-readable <code>client_policy</code> on health, help, and the connection manifest so OpenClaw-compatible clients, Qclaw-style clients, WorkBuddy-style clients, or other local AI clients can consume explicit route, output, sensitive-read, and write-flow boundaries. The local CLI also redacts profile paths, key ids, signing headers, tokens, passwords, and secrets from output.
Current governed execution support covers individually approved proposal execution for explicit Adapter profiles, including <code>npcink-abilities-toolkit/trash-post</code>, <code>npcink-abilities-toolkit/create-draft</code>, <code>npcink-abilities-toolkit/update-post</code>, <code>npcink-abilities-toolkit/update-post-blocks</code>, <code>npcink-abilities-toolkit/update-template-blocks</code>, <code>npcink-abilities-toolkit/upsert-template-blocks</code>, <code>npcink-abilities-toolkit/update-template-part-blocks</code>, <code>npcink-abilities-toolkit/set-post-terms</code>, <code>npcink-abilities-toolkit/reply-comment</code>, and <code>npcink-abilities-toolkit/approve-comment</code>.

Npcink AI Client Adapter

Thin AI client channel plugin for Npcink Governance Core and WordPress Abilities execution.

Haktan Suren

HandL AI Connector Access Control lets administrators allow/deny AI Client prompt execution on a per-plugin basis using the <code>wp_ai_client_prevent_prompt</code> filter introduced with the WordPress AI Client.
Default behavior is allow.
Learn mode (Audit & log tab) logs every AI Client call without blocking, so you can discover callers before enabling deny rules on the Plugin rules tab.
Emergency kill switch blocks all AI Client calls except plugins you list as exceptions.
Caller attribution is best-effort and is determined by inspecting the PHP call stack and mapping file paths to installed plugins.
<h3>Privacy / Data</h3>
This plugin does not send data to any external service.
If you enable recent-call logging in Settings → HandL AI Connector Access Control, it stores a local log in the WordPress options table containing:
<ul>
<li>Timestamp</li>
<li>Allow/deny decision</li>
<li>AI Client operation (e.g. <code>generate_text</code>, <code>is_supported_for_text_generation</code>)</li>
<li>Provider and model when set on the prompt builder (or model preferences)</li>
<li>Truncated prompt preview and selected generation config (best-effort)</li>
<li>Input and output token counts when the AI Client completes a generation (best-effort)</li>
<li>Best-effort calling plugin (plugin basename) and source file</li>
<li>Current user id and display name</li>
<li>Request URI</li>
</ul>
Logs are kept as a count-based ring buffer (default 200 entries, configurable 20–1000). There is no time-based TTL—older rows drop only when the buffer is full.
Logging is disabled by default.

HandL AI Connector Access Control

Control which plugins may execute prompts via the WordPress AI Client.

Npcink AI Client Adapter vs HandL AI Connector Access Control