Your widgets and themes, as files.
Everything the agent builds — widgets, themes, components, templates and snippets — lives in a workspace as real files you can read, hand-edit and sync back. A change is a diff you can review, not an opaque row inside a page builder.
Ship More Client Sites Without Hiring More People*
*Comparing 1 Operator + WPOS to 1× dedicated resource per category.
“WPOS enables AI to be used directly inside WordPress, saving countless hours.”
It completely changes the way my agency builds and manages websites.
The Workspace, answered.
What lives in it, how it stays in sync, and what happens when you want to edit by hand.
The file side of WPOS. Every widget, theme, component, template and snippet the agent builds exists as a folder of real files — a Twig template, a stylesheet, a JSON config — rather than as an opaque row inside a page builder.
Yes. They are ordinary files. Open the template or the stylesheet, change it, sync it back. Nothing about the workspace assumes the agent is the only thing allowed to write.
You pull the current state down, work on it, and push it back, with a status check that tells you what has drifted and a watch mode that syncs as you save. Pulling before you edit is what stops a stale local copy from overwriting live work.
It is already files on disk, so anything that tracks files will track it. That is the point of the format: a change to a widget is a diff you can read rather than a blob you have to trust.
Yes. Widgets, themes and components export as a bundle and import into another site, so a pattern you build once travels instead of being rebuilt from scratch on the next project.
Widgets keep revisions you can roll back to, and page-builder changes are backed up per page and can be restored. The files being readable is part of the same safety net — you can see exactly what changed.
Files on one side, native blocks and modules on the other
A widget in the workspace is a folder of real files, but on the site it behaves like part of the builder you already use. In Gutenberg, every WPOS widget is registered as a block: search the block inserter and it appears under the WPOS category. In Elementor, every WPOS widget is registered as a native Elementor widget under its own WPOS category and renders in the editor with no compatibility warning. In Divi, its widgets work as native modules in Divi 4 and Divi 5.
That is what makes a section reusable without asking anyone to touch markup. On a Gutenberg site, WPOS builds pages from the block editor’s own core blocks, and when a section should be reused or edited by someone who does not write code, you can ask WPOS to make it a widget. A service grid, for example, can become a widget with a repeater, so services are added, reordered and edited from fields instead of code.
Widgets need the WPOS plugin to render. Your builder’s own elements can be edited in that builder, while WPOS widgets have their own editable controls. If you or a client need to change particular text or images in the normal editor, say so in the brief and check it in the result.
Mistakes stay recoverable. Widgets keep revisions you can roll back to, and on Elementor, where a layout saved this way does not create a WordPress revision, WPOS keeps copies of a page’s recent layouts before it rewrites them, so an edit that goes wrong can be rolled back. Because the files are readable, you can always see exactly what changed.
Work also moves between sites. Widgets, themes and components export as a bundle and import into another site. To move a whole site or sandbox onto another WordPress install, its migration key carries the pages and posts with their builder content, the themes and plugins it uses, media, menus and site settings, and the WPOS chats and connected connectors. The source site is not changed, so a move is a copy rather than a handover.
Pull, edit, push, and see what drifted
Each widget folder holds a Twig template, a stylesheet and a JSON config, and the same goes for themes, components, templates and snippets. They are ordinary files: open the template or the stylesheet, change it and sync it back. Nothing about the workspace assumes the agent is the only thing allowed to write.
Syncing has three parts. You pull the current state down, work on it and push it back. A status check tells you what has drifted between your copy and the site, and a watch mode syncs as you save. Pulling before you edit is what stops a stale local copy from overwriting live work.
Because it is already files on disk, anything that tracks files will track it, so a change to a widget is a diff you can read in review rather than a blob you have to trust. Anyone who reads CSS and Twig can work on it, not only whoever knows a particular builder.
Styling stays contained. On a Gutenberg page that needs its own styling, WPOS can keep it in a snippet scoped to that page so it cannot leak into the rest of the site, and on Elementor it sets the theme’s colors up as variables, so recoloring a whole site is one edit.
On a Gutenberg site, pages are made of the block editor’s own blocks, such as cover, columns, quote and group, not wrappers that only WPOS understands, so every section is a real block you can change by hand. On Divi, give WPOS a design such as a Stitch artboard and it can assemble the page from the design’s own exported HTML and CSS instead of redrawing it, or build it again in native Divi modules you can edit module by module.
WPOS widgets carry their own editable controls, so text, images and repeated items can be changed from fields without opening the files. When you move a whole site with its migration key, whatever is on the destination install is replaced, so use a fresh install or one you are happy to overwrite.
More on building and reusing WordPress work across a fleet:
- How to provision a new WordPress client site from your agency playbook Reusing what you already built instead of starting over.
- How to build a WordPress delivery runbook for agency-scale site operations The conventions worth writing down before anyone builds.
- WordPress backup & rollback strategy for agency fleets Where revisions and restores fit in a wider safety net.
- Skills Teach the agent the conventions your files should follow.
- Command Center The panel where you see the site these files render on.
- For agencies What this looks like across a whole book of client sites.
Start free with 15,000 credits.
Three times the usual 5,000, no card needed. Then 50% off your site licences for 2 months with FRIDAY50.
Files you can read beat a blob you cannot.
The docs cover the workspace end to end — or book a free 30-minute demo with the founders and we will walk it on one of your sites.