Nazmul Alam

<p>OctoPress adds an AI workspace inside WordPress admin. It lets site administrators configure their own AI providers, choose models, chat with agent profiles, and use WordPress-aware tools for content and site workflows.</p>
<p>The free plugin focuses on a safe foundation for AI-assisted WordPress work:</p>
<ul>
<li>First-run onboarding for provider setup and readiness checks.</li>
<li>Admin chat workspace with saved chats and per-chat model/agent selection.</li>
<li>Configurable AI providers, including OpenAI Platform, OpenAI OAuth, OpenAI Responses-compatible providers, and OpenAI Chat Completions-compatible providers.</li>
<li>Agent profiles with configurable prompts, skills, handoff behavior, and a default agent for new chats.</li>
<li>Permission controls for approval-gated tool calls.</li>
<li>Block editor content tools for inspecting blocks, patterns, theme design tokens, and composing draft content.</li>
<li>Extension architecture for additional first-party or third-party capabilities.</li>
</ul>
<p>OctoPress stores its operational data in your WordPress database and runs from your WordPress admin. It does not include an AI model. You connect it to the provider and model you choose.</p>
<h4>Runtime requirements</h4>
<p>OctoPress requires PHP 8.1 or newer and working WordPress HTTP loopback requests to its own REST API. The free WordPress.org build uses WordPress-native request ticks for agent runs and WP-Cron as a recovery watchdog. It does not require PHP CLI access, shell access, <code>exec()</code>, <code>shell_exec()</code>, <code>pcntl_fork()</code>, or <code>posix_setsid()</code>.</p>
<p>Some hosts block loopback HTTP requests or disable WP-Cron. In those environments OctoPress can activate, but chat runs may not continue reliably until loopback requests to the same WordPress site are allowed. Sites with disabled WP-Cron should configure a real server cron for <code>wp-cron.php</code>, as recommended by WordPress hosting documentation.</p>
<h4>External services</h4>
<p>OctoPress can send requests to external AI providers after an administrator configures a provider and uses model sync, chat, or an AI-assisted workflow. Depending on the action, data sent to the configured provider may include prompts, chat messages, selected WordPress content, tool context, model names, provider metadata, and generated responses.</p>
<p>Built-in provider options include OpenAI services:</p>
<ul>
<li>OpenAI terms: https://openai.com/policies/terms-of-use/</li>
<li>OpenAI privacy policy: https://openai.com/policies/privacy-policy/</li>
</ul>
<p>OctoPress also supports custom OpenAI-compatible endpoints. If you configure a custom provider, that provider receives the request data for the models you use. Review that provider’s terms, privacy policy, and data handling practices before connecting it.</p>
<p>API keys and OAuth credentials are stored server-side in WordPress and are not returned to browsers by OctoPress REST responses.</p>
<h4>Development source</h4>
<p>OctoPress includes compiled admin JavaScript and CSS in <code>assets/admin/dist</code>. The human-readable admin frontend source is included in <code>assets/admin/src</code>, with build configuration in <code>package.json</code>, <code>package-lock.json</code>, <code>vite.config.ts</code>, and <code>tsconfig.json</code>.</p>
<p>To rebuild the admin assets from source:</p>
<pre><code>npm install
npm run build
composer install
</code></pre>


OctoPress

A WordPress-hosted AI workspace for chat, agents, block content, and provider-managed workflows.

Alley

Matthew Boynes

<p>WordPress has a wonderful editing model with its “draft workflow”, where writers can save unpublished drafts, preview posts, submit drafts for review from a superior, and even schedule a post’s publication. This is all that most writers and teams ever needed for a blog. WordPress has extended beyond blogs, and has grown to be the preferred platform for any person or team writing for the web. While WordPress has evolved, its editing model has not, and this editing model is limited. Once a post is published, edits cannot follow the same workflow. That’s where this plugin comes in. This plugin has two powerful features, the ability to clone posts and the ability to replace posts with another, which combined, allow writers to leverage core’s “draft workflow” for published posts.</p>
<h4>Features</h4>
<ul>
<li><em>Create clones of existing posts.</em> The replicas are created as drafts, and have all the same data (including terms and post meta) as the original post. The only things not cloned are child posts (which include revisions, attachments, and other posts)</li>
<li><em>Replace one post with another.</em> The replaced post becomes a revision of itself, the replacing post is essentially deleted, and you’re left with the replacing post’s data with the post ID and slug of the replaced post.</li>
</ul>
<p>Combined, these features give writers a pseudo-“fork and merge” model. Published posts can be cloned, the clones edited as any other draft can be, then the originals replaced with the clones.</p>
<p>Individually, these features are equally as useful. You don’t need to use the “fork and merge” model to take advantage of this plugin.</p>


Clone & Replace

Gives you the ability to clone posts, and replace posts. Together, you have a very powerful tool for a fork/merge editing model.

OctoPress vs Clone & Replace