Skip to main content
Start free →

Product

Features How it works The Agent Safety & security About

Resources

Cookbook Blog Docs Support Alternatives
Pricing Account
Blog John (I'm not AI) Turner

Lots of Little Wins: Everything Else in WPVibe 1.7 and 1.8

Wapuu wearing a tool belt and raising a wrench, with a speech bubble reading Lots of little wins
Featured illustration includes Wapuu © Kazuko Kaneuchi, licensed under GPLv2.

The last two WPVibe releases each had a headline feature, and we’ve spent this week writing about them: code snippets, Elementor v4, the page audit, SeedProd pages that finish themselves.

This post is about everything else. The two dozen smaller changes in 1.7 and 1.8 that don’t demo well but decide whether the product feels dependable. If the big features are why you try WPVibe, this list is why you keep it.

Your AI guesses less

Every error WPVibe reports now carries structured facts: what actually went wrong, whether retrying could possibly help, and whether the connected account even has the permissions for the job. That sounds bureaucratic until you watch what it fixes. The AI stops re-trying things that cannot work, stops suggesting “reconnect your site” when the real problem is a permissions gap, and starts saying things like “your account can’t edit themes, here’s who can.”

Permission errors also got specific. Instead of WordPress’s generic “you are not allowed to do that,” the AI now sees which capability is missing on which post type, and can tell you in plain English.

Publishing survives picky hosts

Some hardened hosts block deleting theme folders, which used to be able to interrupt publishing a new design. Publishing now swaps folders instead of deleting and recopying, and if anything goes wrong mid-publish, a complete backup is kept and the error says exactly where it is. Boring, load-bearing, exactly how we like it.

Fewer false alarms

  • Commands carrying punctuation inside quoted text (an SEO title with a pipe, a serialized setting) are no longer rejected as unsafe. Quoted values are data, not commands.
  • Content that mixes single and double quotes now round-trips byte for byte instead of silently losing characters.
  • Searching your settings for something like blog_ now treats the underscore as an underscore, not a wildcard that matches half your database.
  • Long posts with emoji or accented text no longer get mangled when previews truncate them.

Approvals got even more honest

The approval panel is WPVibe’s core safety promise, so its previews have to be exactly right. Two fixes there: deleting a user by email address now shows the real account details in the preview (it previously could claim the user wouldn’t be found while the deletion would still proceed), and the bulk transient cleanup preview no longer overstates what it deletes. If a preview and an action can disagree, the preview wins; that’s the standard we hold it to.

On the hardening side, database queries now reject a MySQL trick (executable comments) that could hide a blocked keyword from the safety checks. You’ll never notice. That’s the point.

Quality-of-life, rapid fire

  • “Any theme updates?” is now one question. Theme listings report update availability the same way plugin listings have for a while.
  • Organizing content works everywhere. Your AI can now assign existing categories, tags, and custom taxonomy terms to posts, including the private taxonomies plugins register that normal integrations can’t reach. It never invents terms; a missing one is reported with how to create it.
  • Big settings, small reads. The AI can pluck a single value out of a large plugin settings blob instead of hauling the whole thing into the conversation. Faster answers, less noise.
  • Long pages, no more cliffhangers. Reading a very long page no longer cuts off at the end of what fits; the AI pages through the rest.
  • Stay signed in. Connections now last a full day instead of demanding a fresh sign-in every hour. Small change, noticeably less friction.

The pattern behind the list

Almost everything above came from watching real sessions: places where the AI guessed, retried, over-asked, or trusted a preview that was subtly wrong. We fix those one at a time, every release. Individually they’re too small to announce. Together they’re the product.

If you want the headline features, the rest of this week’s posts cover them: the full list is on the blog. If you just want a site that does what you ask, connect and ask.

One more for the road: this week’s plugin update also put a WPVibe widget on your wp-admin dashboard. Connection status, what your AI changed recently, and recipes picked for the plugins you actually run. We’ll give it a proper post soon.

Thanks for reading along all week.

John and the WPVibe team

P.S. Everything in this post, and everything we announced this week, is free. Get started at wpvibe.ai/start, or install the WPVibe plugin from WordPress.org.