Run multiple agents on your WordPress site in parallel.
Onumia is a WordPress plugin that gives every task its own isolated sandbox, so agents work in parallel on the same site without colliding. Each one runs against a real copy of your data, and you preview every change before it goes live.
• Creating sandbox
└ pricing-refresh · isolated database and Agent Code
Production stays live. No visitor sees it yet.
• Applying changes
└ Updated pricing copy, hero call to action, and FAQ order
• Changes have been applied
Preview → acme-store.com/sandbox/pricing-refresh
• Showing changed entities
+ Pricing page copy
+ Hero call to action
~ FAQ order
Promote to publish it live, or discard to throw it away.
gpt-5.5 high · acme-store.com
How it works.
Install the plugin and connect your agent. It works in a private copy of your site, so you can preview each change and either take it live or throw it away. Nothing reaches the live site until you say so.
01 Connect your agent
Any MCP agent connects through a WordPress Application Password, as a real user with the role and capabilities you grant it.
production
wp_posts
wp_options
sandbox
wp_3f9a_posts
wp_3f9a_options
db.php swaps the table prefix
02 It works on a copy
A db.php drop-in clones your tables under a sandbox prefix and points the whole site at the copy, so the agent reads and writes real data while production stays put.
03 Preview the result
A one-hour, preview-only link renders the sandbox inside WordPress, so you see the change before anyone else. It cannot run commands or promote.
wp_options merged
wp_posts merged
wp_usersunchanged
only what changed merges back
04 Promote or discard
Promoting runs a git merge plus a three-way database merge, applying only what changed back to your live site. Discard, and the sandbox is dropped.
Ask in plain language.
Point an agent at your site and describe the change. It works across the plugins you already run, with nothing to wire up per tool.
Add a sale badge to every WooCommerce product on sale
Translate the homepage into German with Polylang
Bump all WooCommerce prices by 10% for the summer sale
Add a new download and a launch discount in EDD
Rewrite meta titles and descriptions for my top pages in Yoast
Spin up an Elementor landing page for the webinar
Tag every repeat customer in FluentCRM
Sync new subscribers to my Mailchimp audience
Connect any MCP-capable agent.
Onumia connects through WordPress Application Passwords, so any MCP-capable agent gets the same sandboxed access, the same command modes, and the same promote-or-discard handoff. Bring the agent you already use.
Made for your whole WordPress stack.
No per-plugin integrations to build, no skills to maintain. Agents search and read the actual, current code of your themes and plugins, so Onumia works with your whole WordPress stack out of the box.
Agents that act like a developer.
An agent inspects and changes the site the way a developer would, working from what is really there instead of guessing. Every edit happens in its own copy first.
- Search core, plugins, themes, and content
- Run WordPress commands
- Write code in the Onumia Agent Code plugin
- Preview before anything is promoted
wp-content/plugins/acme-store/api.php
42 register_rest_route( ‘acme/v1’, ‘/orders’, [
88 register_rest_route( ‘acme/v1’, ‘/cart’, [
131 register_rest_route( ‘acme/v1’, ‘/coupons’, [
wp-content/plugins/acme-store/checkout.php
17 register_rest_route( ‘acme/v1’, ‘/pay’, [
53 register_rest_route( ‘acme/v1’, ‘/refund’, [
wp-content/plugins/acme-reviews/rest.php
29 register_rest_route( ‘acme/v1’, ‘/reviews’, [
wp-content/themes/acme/functions.php
240 register_rest_route( ‘acme/v1’, ‘/menu’, [
4 files · 7 matches · 24 ms
One tool to rule them all.
Agents are fluent in one language above all others: the shell. So Onumia hands them a single execute tool and a real bash environment to use it in. Every command is parsed, sorted into read, write, or eval, and checked against the agent’s capabilities, so you decide what counts as allowed before a character runs.
Acme Store
7
Success: Updated post 42.
refused, the agent has no execute_eval
Real bash
Pipes, loops, redirects, subshells, and conditionals. The agent writes the shell it already knows.
Parsed before it runs
A control layer parses every command into a syntax tree before it reaches the shell, so Onumia knows exactly what it will do.
Classified and gated
Every command is sorted into read, write, or eval, and refused before it runs if the agent lacks the capability.
Safe wp eval
wp eval runs through an AST validator, never a raw eval, so PHP can’t break out of the sandbox.
Real changes, previewed before they ship.
Agents are at their best on the real thing, and that’s exactly where a wrong move does damage. Onumia routes every task through the same short loop, so changes are real but nothing ships until you promote it.
01
Create a sandbox
Start from a private, isolated copy of the live site.
02
Let the agent work
It edits code and content, fully away from production.
03
Preview the result
Open the change in WordPress before any visitor can.
04
Promote or discard
Ship it live when it is right, or remove the sandbox cleanly.
A sandbox is the unit of work.
Each task gets its own isolated copy of the site, living right inside the same WordPress install: a private database, an editable Agent Code checkout, and its own preview. The agent edits the copy, not the live site.
Isolated database
Its own copy of the data. Live data is never written.
Editable Agent Code
A real plugin checkout the agent can build inside.
Run many in parallel
Several tasks and agents at once, with no collisions.
One protected site, many sandboxes
on apply pricing
updated copy + CTA
reordered the FAQ
preview ready
on add faq block
+ 6 questions
building preview
awaiting review
on prune drafts
scanned 240 posts
– 12 stale drafts
needs another pass
Many agents, many tasks, no collisions.
Because every sandbox is fully isolated, different agents can run different tasks at the same time. No one’s work can overwrite anyone else’s, and nothing reaches the live site until you promote it.
Edit a copy. Merge what changed.
Every task gets its own copy of your live database, so the agent does real work on real data and nothing changes live until you promote. Then only what actually changed moves back.
Production
livewp_options
wp_posts
wp_postmeta
wp_users
The original tables.
Sandbox
agentwp_onumia_3f9a_options edited
wp_onumia_3f9a_posts edited
wp_onumia_3f9a_postmeta
wp_onumia_3f9a_users
The agent edits a copy.
Production after promote
mergedwp_options merged
wp_posts merged
wp_postmeta kept
wp_users kept
Only what changed is merged back.
Permissions that match how WordPress already works.
Every agent connects as a real WordPress user. What it can do, from read-only commands to promoting database changes, is governed by capabilities you assign per role. Administrators tune these in settings; defaults are shown here.
| Role | Create | Read | Write | Eval |
|---|---|---|---|---|
| Administrator | ||||
| Editor | ||||
| Author | ||||
| Contributor | ||||
| Subscriber |
Full access isn’t the same as safe.
Hand an AI agent direct access to your site and it holds the keys to everything live, with no way to catch a wrong move first. Onumia gives every task its own sandbox you can preview and promote, so changes are reviewed before they ever go live.
The usual way
- Changes hit the live database
- All-or-nothing permissions
- Safe only on a throwaway staging site
- You babysit every action
- No way to stage and approve a whole task
With Onumia
- Every task runs in its own sandbox
- Capabilities assigned per role
- Safe to run on staging or production
- Preview the whole change first
- Promote when ready, or discard
Guardrails at every layer.
Onumia does not rely on a single switch. Access is constrained at every step, from who connects to what reaches the live site.
WordPress identity
Every agent connects as a real WordPress user through Application Passwords.
Role capabilities
What a user can do is set per role, and nothing beyond it.
Sandbox isolation
Unfinished code and data stay in the sandbox until you promote it.
Preview-only tokens
A preview link shows the sandbox. It cannot run commands or promote.
Explicit promotion
Going live is a deliberate step an administrator approves.
Full audit log
Every command, tool call, and promotion is recorded.
What teams ship with Onumia.
Real WordPress work that used to be risky to hand an agent, now safe to run on the site that matters.
Content refreshes
Rewrite copy, reorder sections, and update pages without risking the live site.
New functionality
Build a shortcode, block, or endpoint in Agent Code, then promote it.
Bulk cleanup
Prune stale drafts, fix metadata, and tidy taxonomies at scale.
Migration prep
Stage and review structural changes before they touch production.
Questions, answered.
What you need to know before pointing an agent at your WordPress site.
A plugin. You install it on your own WordPress site, and every sandbox is an isolated copy of that site’s database and code that lives inside the same install, not a separate server or service.
Yes. Every task works in an isolated sandbox and only reaches the live site when you promote it, so it is safe to point at production, or at a staging site if you prefer.
Yes. Every task gets its own sandbox, so many agents and people can work the same site in parallel without colliding.
Exactly what you allow. Capabilities are assigned per WordPress role, so an author might only inspect while an editor can prepare changes.
Any MCP-capable agent. Onumia connects through WordPress Application Passwords, so you bring the agent you already use.
No. Onumia sandboxes are isolated, previewable copies on the same site, so a separate staging environment is not required.
It is marked inactive and its preview stops working. Nothing from a discarded sandbox reaches the live site.
Review and promote, visually with Pro.
Pro adds a browser workspace on top of the free sandbox: preview a sandbox like a real site, promote exactly the changes you choose, and roll back safely.
Live sandbox previews
Open any sandbox in a real in-browser preview and click through the change before it ships.
Visual selective promotion
See changes grouped the way you think about them and promote only the parts you choose.
Drift-safe rollback
Every promotion is reversible, with a drift check that blocks an unsafe undo.
Put a whole team of agents on your site.
Install Onumia, connect the agents you already use, and let them run in parallel on the same site, each in its own sandbox you control.