Inside the PHP sandbox

Automation often needs a little server-side code: a scheduled cleanup, a custom endpoint, a one-off migration. NIBWP gives agents a dedicated, auto-loaded PHP sandbox to author that code — isolated from your theme and core files.

A folder of its own

The sandbox lives in its own directory under wp-content. Files there are auto-loaded on every request, so an agent can write a small PHP file and have it take effect without touching functions.php or a plugin you maintain.

Why isolation matters

Mixing agent-authored code into your theme is how sites break. Keeping it in a separate, clearly named folder means you can review everything in one place, disable it instantly, and never wonder whether an edit came from you or an agent.

• Separate from theme and core, so reviews are simple.
• Auto-loaded, so no wiring is required.
• Plain files on disk, so version control just works.

Powerful, but never tangled into your theme.

Gated like everything else

Writing to the sandbox is a privileged operation. It is scoped per token, recorded in the audit log, and — because it can execute PHP — best used on staging with backups in place. The same least-privilege model that governs content writes governs the sandbox.

What teams build with it

Recurring content jobs, data backfills, custom REST routes for an internal tool, and quick experiments that would otherwise need a full plugin. When the experiment graduates, you lift the file out and ship it properly. See the docs or book a demo.