Nazmul Alam

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.
The free plugin focuses on a safe foundation for AI-assisted WordPress work:
<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>
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.
<h4>Runtime requirements</h4>
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>.
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.
<h4>External services</h4>
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.
Built-in provider options include OpenAI services:
<ul>
<li>OpenAI terms: https://openai.com/policies/terms-of-use/</li>
<li>OpenAI privacy policy: https://openai.com/policies/privacy-policy/</li>
</ul>
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.
API keys and OAuth credentials are stored server-side in WordPress and are not returned to browsers by OctoPress REST responses.
<h4>Development source</h4>
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>.
To rebuild the admin assets from source:
<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.

shawfactor

This plugin allows you to archive your WordPress content similar to the way you archive your e-mail. Unlike other archiving solutions though this actually does it all and does it properly
<ul>
<li>Makes a new post status available in the drop down called Archived</li>
<li>Hides or removes your content without having to trash the content</li>
<li>Content can either be hidden entirely from public view or simply from the main loop and feed and pages, with other solutions you can only hide it from public view.</li>
<li>Allows you to add a label to the title of those posts/pages etc that are archived</li>
<li>Allows you to add a message to the top of the post/page etc that the content is no longer up too date</li>
<li>Allows you to set an archiving date after which content is automatically changed to having an archived status</li>
<li>Compatible with posts, pages and custom post types</li>
</ul>
This plugin is ideal for sites where certain kinds of content is not meant to be evergreen
Like this plugin? Please consider <a href="https://wordpress.org/support/view/plugin-reviews/lh-archived-post-status/" rel="ugc">leaving a 5-star review</a>.
Love this plugin or want to help the LocalHero Project? Please consider <a href="https://lhero.org/portfolio/lh-archived-post-status/" rel="nofollow ugc">making a donation</a>.

LH Archived Post Status


When Automattic developed WordPress, it had a crazy notion of what an 'archive' is. 20+ years later, we're stuck to the same definition: WP considers that an 'archive' is really just a list of past articles, neatly ordered by month/year.



But that's not the case. A real Archive is a place where you can store posts that are not relevant any longer — thus keeping them away from the Loop — but without deleting them, because, naturally enough, the whole point of having an Archive is to allow search engines and backlinks to 'old' articles to still work correctly.



This is the whole point of this simple plugin: to allow to add a new status to every post/page, classifying it as having been archived. This means that the post/page will not require any changes: it doesn't need to be deleted, change its category, add any tags, or simply set to Draft (so that it doesn't appear). Instead, posts and pages stay exactly as they were before — just with a new status (beyond the classic ones, i.e., published, private, draft).



Because this status is an addition, this means that all well-behaved plugins and themes will not recognise it as a valid status (i.e. when checking if a post is published, the theme/plugin will not find the archived posts), and so they effectively 'disappear' from the visibility status of most 3rd party code. That's exactly what we expect to happen with an 'archived' post. And that's precisely what this plugin does, and does quite well; as such, it comes as highly recommended by many reviewers, and ranks high on their lists of 'best' plugins for a specific purpose.



The plugin itself is well-written, strictly follows all coding guidelines as set by Automattic and the developer community, regularly maintained, and has very reasonable support on the forums: issues are opened, followed up by the author, and closed when resolved or when threads become stale due to lack of activity. Documentation is minimal, because the plugin is so simple to activate and use (and not because anything is missing).



Sadly, at the time of writing this (July 2023), this plugin suffers from a dependency of a third-party library which, unfortunately, breaks the posting workflow, introducing a new way of saving new posts which is not only counter-intuitive, but lacks essential functionality. Work is under progress to restore the normal functionality of the posting workflow, but, until that happens (which is beyond the plugin author's control), it means that you very likely won't wish to use this plugin on any WordPress site that is used by more than one author.



I will certainly review my classification in the future, once this major issue gets resolved, and LH Archived Post Status works again, flawlessly integrated into the WordPress posting workflow, as it did in pre-Gutenberg days.


If you need to have a real Archive, this is the plugin you want

Allows posts and pages to be archived so you can remove content from the main loop and feed without having to trash it.

OctoPress vs LH Archived Post Status