Before you update
This release removes the [acrossai_mcp_servers] shortcode and the embeds block. Both have moved to AcrossAI Pro.
If you have that shortcode on a page it will stop rendering, and the page will show nothing in its place. Install AcrossAI Pro first if you rely on it.
Everything else is safe: servers, connections, abilities and access control are untouched, nothing needs reconnecting, and there is no database change.
Removed
The front-end embed shortcode and block. [acrossai_mcp_servers], the per-server Embeds tab and the transports behind them have moved to AcrossAI Pro, where the rest of the publishing surface already lived. No connected assistant notices the difference.
New
A Troubleshoot screen that says why an assistant cannot connect. Until now the admin showed nothing when a connection failed — the assistant reported its own unhelpful error and every check you could reach said the site was healthy, because it was. AcrossAI → Troubleshoot probes this site the way an assistant does and reports eight checks, each with a plain-language reason and, where it helps, text to paste into a hosting ticket. It runs only when you press the button, and it changes nothing.
It names the plugin that is blocking you. If something refuses unauthenticated access to the REST API — which blocks the first step of every connection, before any credential exists — the screen names the plugin responsible and quotes the error it returned, instead of saying "a security plugin" and leaving you to deactivate thirty of them one at a time.
It checks what actually breaks connections. Whether a cache is serving an assistant a stale copy of your connection details; whether a security rule rejects non-browser visitors (Claude connects as python-httpx, and "block Python" rules ship switched on in some firewall plugins); whether the OAuth addresses resolve at all; and which caching or security layers sit in front of the site.
It is honest about its own blind spot: every check runs from the site to itself, so it cannot see a block based on where the visitor connects from — and it says so rather than showing a green tick.
Let your AI client set itself up. Alongside the manual instructions for all sixteen supported clients, there is now a block of text you can paste into the client, telling it to open its own configuration file and add the server. Same configuration either way.
Fixed
Your site told every cache to keep its connection details for an hour. The documents an assistant reads to learn how to connect were served with a sixty-minute cache instruction, and nothing told page caches to skip them. On one site that meant an operator fixed a real problem, tested again, and still failed — for an hour, with nothing anywhere indicating a cache was involved. The window is now sixty seconds, page caches are told explicitly not to store these documents, and changing a server's address or switching it off purges the affected documents immediately.
OAuth addresses could 404 until you re-saved Permalinks. Four addresses an assistant needs are built from WordPress's permalink rules, and those rules can go missing for reasons unrelated to this plugin — another plugin rebuilding them, a database copied from a site where this plugin was switched off, a restore. The plugin only noticed when its own version changed; the rest of the time the fix was to visit Settings → Permalinks and press Save. It now verifies the rules are present on each admin page load and repairs them itself. A site on Plain permalinks is reported separately, because those addresses can never work there.
The activity log screen had no styling at all. It had been running on browser defaults since it shipped: four stat boxes floating loose, a table with no header band or row lines, and columns filling barely half the screen. It now has the layout it was designed with, plus a column showing roughly how many tokens each response returned.
A permanent warning on sites that will never need it. The notice about WordPress scheduled tasks being switched off appeared on every admin page, forever, on every local and staging install — to report that a clean-up with nothing to clean would not run. It now appears only once there is OAuth data to clean up, and a site running scheduled tasks from a real cron entry can say so and silence it for good.
Changed
"Activity" is now "Logs". The menu entry, page title and web address all say Logs, matching the per-server tab that was already called that. Any bookmark to the old address needs updating.
The AI Connectors panel matches each assistant's real dialog. The steps for Claude, ChatGPT, Gemini, Grok and Cursor had drifted from what those products actually show. Each has been rewritten against the current dialog with fields named as they appear on screen, and Claude gains a one-click button that opens its connector dialog pre-filled.
Full changelog: v0.4.5…v0.4.6