Skip to main content
Build (also known as Direct Edits) is how Foenix makes changes to your WordPress site. You describe what you want - Foenix executes it and reports back. Every change passes the read-only Verifier agent before it counts as done: it checks whether the task was actually completed, not just whether it ran. How the pipeline works →

​
What Build can do

  • Create and edit posts, pages, and custom post types
  • Modify theme files - PHP templates, CSS, JavaScript
  • Create or modify plugins
  • Add snippets to functions.php
  • Change WordPress settings, menus, and widgets
  • Generate and set featured images
  • Create site files such as llms.txt to make your site AI-ready
Adding code snippets to functions.php can break your site if something goes wrong. Always make a backup at the hosting level before doing this. Backups →

​
Example

You say:
Foenix executes:
  • Adds CSS to style.css
  • Adds JavaScript to main.js
  • Adds the button HTML via a hook in functions.php Then reports back with what was changed and, when available, a Rollback option.
Heavy tasks, for example a full page build with several sections, are split by the Orchestrator into parts, each handled by its own Worker sub-agent. You see one result, but each part was planned and verified separately. Architecture →

​
Rollback

After actions that modify your site, a Rollback button may appear in the session. Use it to undo the last change if something didn’t work as expected. If a change could not be undone, Foenix tells you right away instead of reporting a false success. Learn more →

​
Safety modes

How carefully Foenix validates its own actions depends on the selected Safety Mode. We recommend keeping it on Balance for production sites. Learn more →
Always make a backup before running edits on a production site, or rehearse the task in a Cloud Site first. Backups →