An open AI development framework for WordPress
Guided agents that read your site, write out what they intend to do, and wait for you to approve it. Open source, provider-agnostic, and read-only until you say otherwise.
Alpha software. Install on a test site before production.
This is what it looks like inside your dashboard
A simulated WordPress admin with the engine installed. Use the controls at the bottom to change the theme, dock it as a sidebar, float it, or watch it run a debugging pass. Nothing here touches a real site.
Welcome to FB Software AI Engine!
Your WordPress setup assistant — step-by-step video guides, admin shortcuts, and clear website-building workflows.
Step-by-Step Guides
Easy tutorials for every task.
Admin Shortcuts
Quick access to key screens.
Security First
Protect and manage your site.
Work Smarter
Save time on repeated steps.
Website Settings
Complete your WordPress settings
- ✕ Set the Homepage
- ✕ Set the Blog Page
- ✕ Configure Permalinks
- ✓ Set Title & Tagline
Plugin Setup
Essential plugin setup
- ✕ Install Elementor
- ✕ Install Site Kit by Google
- ✕ Install a Backup Plugin
- ✕ Install an SMTP Plugin
Website
Steps for your website
- ✕ What to do before starting
- ✓ Make a Back-up
- ✓ Install a Theme
- ✕ Create Main Pages
Help and Tutorials
Help & tutorial resources
- ✕ Watch the Welcome Video
- ✕ Open Guide Videos
- ✕ Open Documentation
- ✕ Contact Support
Read-only debug mode. I inspect and report — no changes without approval.
Simulated interface. No WordPress install, no plugin, no network calls.
Best viewed on a larger screen — the admin layout is condensed here.
What it can be asked to do
A fixed set of commands, not open-ended instructions. The list grows as each one is built and tested.
Check for errors
Read-onlyScans logs, plugin state and settings, then reports what it found without touching anything.
Show progress
Read-onlyReports the current state of the install — versions, active plugins, published and draft pages.
Create an About page
Adds one draft page with heading, intro and founder sections. Left unpublished for you to review.
Create all main pages
Home, About, Services, Blog and Contact as drafts. Anything that already exists is skipped, not duplicated.
Install a theme
Installs from the WordPress theme directory without activating it. Switching themes needs its own approval.
Make a backup
Exports the database and archives uploads, themes and plugins to a folder on your own server.
“I could not map that request to a safe demo command.”
What it says instead of improvising
Four things that make it different
Read-only by default
It opens unable to change anything. Inspecting, reporting and diagnosing are always safe.
Plans you can read
Actions arrive as numbered steps in plain language, before they run — not as a log afterwards.
It won't guess
Requests it can't map to a known command get refused, with a list of what it can actually do.
Open and portable
The code is public. You bring your own provider, and the site stays yours to move.
Four steps, on a test site first
The engine is alpha. Treat it like alpha and you'll have a good time with it.
-
Set up somewhere disposable
A LocalWP install or a staging site. Not the site your customers are looking at.
-
Install the plugin
Upload the ZIP through Plugins → Add New → Upload, then activate it.
-
Add your provider key
The engine doesn't ship with one. Paste your own key in settings and it will confirm the connection.
-
Start in read-only
Ask it to inspect the site before you let it write anything. Get a feel for how it reports first.
Read the code before you trust it
Everything is on GitHub while it's being written. If you'd rather learn the ideas first, track two of the tutorials walks through the whole thing.