# Product updates
Source: https://docs.foenix.ai/changelog
New features, improvements, and fixes to Foenix.ai
## Agents: Worker replaces Architect
* **Meet Worker.** The Architect agent is retired. On a heavy, long task the Orchestrator now decomposes it: splits the task into parts and calls a dedicated Worker sub-agent for each one. The result is noticeably higher accuracy and consistency across multi-step jobs.
* **Verify is stricter and more honest.** It now checks whether the task was actually completed, not just whether it ran.
* **Pause only pauses the schedule.** Pausing a Scheduled Agent stops its next timed runs. Sessions already in progress, including ones started with Run Now, keep going.
## Rollback: honest by design
* **Rollback reports the outcome honestly.** If a change could not be undone, you find out right away instead of discovering it later. Every WordPress stack is different, and we keep extending rollback coverage to new configurations.
* **Undo now covers long posts** with images and SEO meta, which previously could fall outside rollback.
## Make your site AI-ready
* **llms.txt and similar files can now be created.** Ask Foenix to bring your site up to speed for AI crawlers and add llms.txt.
## Cloud Site, formerly Sandbox
* **Sandbox is now Cloud Site.** Your sites are labeled Cloud Site or Self-hosted, and the demo one shows "Demo site expires in".
* **500 bonus credits when you connect your own site.** One time, on the first site you connect.
## Live mode
* **The current page URL is shown,** clickable, with long paths shortened.
* **Links to your site's pages open in Live mode.** Session results now use three link styles so you can tell them apart: green for files created inside Foenix, orange for WP Admin, grey for external.
## π Fixes
* **Files** not reaching the chat, or opening with a 404.
* **Responses occasionally switching language** mid-session.
* **Plugin:** table creation on update, transaction errors during install. Update to the latest plugin version.
* **Requests hanging** with no response until a page reload.
## New
* **Pull-only plugin mode.** If your firewall blocks incoming requests, the plugin can now work in pull-only mode, so Foenix connects to sites that were previously unreachable.
* **New Agent, your way.** The New Agent button now opens a choice: build the agent through a chat, or fill in the setup form yourself.
* **Continue an agent session.** A finished agent's session can now be picked back up simply by writing a message into it.
* **ZIP files are now readable.** Upload a plugin or theme archive and Foenix will unpack it and read the files inside.
## Faster and steadier
* **Sandboxes launch noticeably faster.** They are now prepared in advance, with the plugin version kept current, so you spend less time waiting.
* **Faster dashboard and project opening.** Fewer round trips to the server on every screen.
## Chat
* **Hover a message to see when it was sent.**
* **Improved the UI on mobile devices.**
## Fixes
* **Critical:** sessions that could hang without completing are fixed, along with the credit accounting behind them.
* **Buttons that needed several clicks** now respond the first time, and show progress when the server is slow.
* **Rollback now reports honestly.** If a change could not be undone, you are told, instead of seeing a false success.
## Sandbox: relaunch anytime
* **Launch a fresh 24-hour sandbox whenever you need one.** If your trial sandbox has expired, spin up a new one right from the dashboard. The button activates as soon as your previous sandbox winds down.
* **Expired sandboxes are now cleaned up right on schedule.**
* **WP Easy Migrate is now available as a direct download.** Install it on any WordPress site, not just inside a sandbox. [Guide and link in the docs](https://docs.foenix.ai/get-started/wp-easy-migrate).
## Scheduled Agents
* **Memory for Scheduled Agents.** Scheduled Agents now retain knowledge of your WordPress site between runs.
* **Cleaner responses:** stray internal reasoning no longer leaks into replies, and action formatting glitches are fixed.
## Quality of life
* **Email when your task finishes.** Start a generation, walk away, and we'll let you know when it's done.
* **Connection-loss handling.** If your internet drops mid-generation, you'll see a clear notification and your message returns to the input box, ready to resend.
* **Google sign-in now runs in the same tab,** with no popup.
## Fixes
* **Critical:** password reset was not working. Fixed.
* **Images:** image generation and image analysis both back to normal.
* **Plugin:** activation error when activating immediately after install is fixed. Connection issues for some sites are fixed. The Update button now takes you to WP Admin as expected.
* **Generation pipeline:** a large batch of fixes and corrections in the places where errors occurred.
## Sandbox migration β as promised
Two weeks ago we said our own migration plugin was coming. It's here:
* **WP Easy Migrate** β our migration plugin, now preinstalled in every sandbox. Move an existing WordPress site (database + files) into a sandbox, or take what you built in a sandbox out to any WordPress site.
## Smoother start
* **Straight into your workspace after signup** β no interstitial page, your sandbox spins up while you watch.
* **Live launch status** instead of a generic spinner: "Spinning up WordPressβ¦ Installing the foenix pluginβ¦ Preparing your sandboxβ¦"
* **Email when your demo sandbox is ready** β even if you didn't wait around, you can come back with one click.
* **WP Admin button** right next to your sandbox domain.
* **Pin/unpin sandboxes** on the dashboard.
## Agents & models
* **Standard mode is now Plus.** Lite runs on a mix of fast, lightweight models; Plus and Ultra use larger, more capable models.
* **Plus and Ultra modes are now exclusive to paid plans.**
* **Agents created from a chat now inherit that chat's model mode** β start in Lite, and the agent runs in Lite too, image models included.
* **Run Now** on an agent takes you straight to the created session.
* **Multi-provider model routing** for faster, more reliable responses in Lite mode.
* **Updated Prompt Library** and redesigned quick-start chips.
## π Fixes
* **Files:** improved reading of uploaded text files. File names with spaces handled properly.
* **Sessions:** response arriving but the interface not updating β fixed. Infinite loading β fixed. "Thinking" indicator stuck after a task finished β fixed. Empty responses in Review + Lite β fixed.
* **Plugin:** plugins being unexpectedly deactivated on connected sites β fixed.
* **UI:** double-click needed on preview and pricing buttons β fixed. Zip file downloads β fixed. Wrong mode shown on a newly created agent β fixed.
## Sandbox: built end-to-end
Sandbox went from early access to a real, stable feature this cycle:
* **Sandboxes deploy fast** β without a long wait to get one running.
* **One-click WP Admin access.** Links Foenix generates while working on your site (installing a plugin, opening a settings page) now log you in and take you straight there β no more dead links.
* **Real-time deploy status.** Sandboxes report Deploying β Live as they come up, and you can now launch multiple sandboxes in parallel.
* **Transparent, correct pricing.** 5GB (12 credits) / 10GB (20 credits) / 25GB (30 credits), with disk sizes that actually match what you picked.
* Free / Starter / Pro sandbox limits now enforced correctly across the board.
## Agent system: fully reworked
* **Three model modes.** Lite (MiniMax M3), Standard (Gemini 3.5 Flash), Ultra (Claude Sonnet 4.6) β chosen per session, plus an independent image-model selector.
* **Mode choice locks in per session** once a task starts, so it can't silently change mid-run.
* **Orchestrator and Automation agents fully aligned** β scheduled/automated runs now behave exactly like the agents you configure manually.
* **Stopping a task no longer loses context** for follow-up requests in the same session. Added a proper Stop button.
* **Prompt-caching rework** that meaningfully cuts wasted token cost on longer sessions.
* **New Prompt Library** and quick-start chips β one click to launch ready-made recipes (daily blog post with images, weekly SEO audit, and more).
* Faster responses in Lite mode via priority processing for MiniMax M3 and other lightweight models.
* Fixed token/cost accounting across our models β including a caching double-count bug and garbled Flash responses.
* Fixed autonomous agent lists not filtering correctly by site.
## New
* **Review and Publish.** Choose where the result goes: **Review** prepares files for you to check first, **Publish** applies changes to the live site at once.
* **Redesigned auth pages** β sign-up, login, password reset, and confirmation.
* **Dashboard tiles:** new sites now appear at the top.
* **File previews** now render content directly in a modal (with a download button) for more file types.
* Renamed **Vibe Coding β Live** β opens a preview of your site where you can turn on **Visual Edit** mode.
* **Universal links.** Out of credits mid-task? Agents can now point you straight to the pricing page or the buy-credits modal.
## π Fixes
* **Auth:** Google sign-in occasionally failing on first attempt β fixed. Free-plan bonus credits now correctly granted on Google sign-up.
* **UI:** Long names now display correctly in your profile. Dashboard load-time fixes. General polish across profile, sessions, and mobile layouts.
* **Plugin:** Connection errors now shown clearly on the plugin settings page.
## New
* **Gemini 3.1 Pro** now available on production across all agents.
* **Credit packs now available on Starter plan.** Previously limited to Pro only.
* **Session titles** now generated from chat context for easier browser history navigation.
## π Fixes
* **Critical:** WP plugin returning empty response on code execution β fixed, further improvements in progress. βοΈ
* **Critical:** Plugin not loading dashboard on first connect β fixed.
* **Billing:** Complete rewrite of credit counting logic.
* **Billing:** Overage no longer deducted from future purchases or renewals.
* **Billing:** Credit pack expiry corrected to 6 months.
* **Billing:** Upgrade/Downgrade blocked correctly when renewal not allowed.
* **UI:** Interface locked during backend requests β fixed, monitoring ongoing. βοΈ
* **UI:** Skeleton animation added to profile β prevents errors from clicking before data loads.
* **UI:** Edit agent panel moved to bottom of session with next run time and status visible.
* **UI:** Vibe Coding top bar layout fixed.
## New
* **Gemini 3 Flash** added as a model option alongside Claude Sonnet 4.6. Choose per task β Flash for speed and cost, Sonnet for complex builds. Configure in **Settings β Personality β AI Pipeline Models**.
* **Create Autonomous agents from any session.** While in Conversational mode, just describe the task and tell Foenix when and how often to repeat it β for example, *"every Monday at 9am, audit my SEO and email me the report"*. Foenix expands it into a full prompt and shows a **Schedule Task** card to confirm.
* **Stop a running task at any time.** You can now interrupt a task before it finishes β useful when you spot it heading the wrong way or just want to cancel and try a different prompt.
* **Per-agent model selection.** In your Profile, you can now choose which AI model each agent uses individually β pick a lighter, cheaper model for simple recurring tasks and a more powerful one for complex builds.
## π Improvements
* A batch of bug fixes across the platform. We're watching closely and shipping improvements continuously β keep the feedback coming.
Foenix.ai is in active early development. We've been building for the past 6 months and this is our current feature set.
### What's available today
* **Multi-Agent architecture** β Foenix operates as four specialised agents (Orchestrator, Architect, Coder, Verifier) with built-in retry-on-failure logic. See [Architecture](/core-concepts/architecture).
* **Rollback** β undo file-level changes (in active development)
* **Safety modes** β three levels (Safe, Balance, Hard) to control how strictly Foenix validates actions
* **Multi-site dashboard** β manage multiple WordPress sites from one account
### Honest note
This is an early version of the product. We recommend using Foenix always keeping backups at the hosting level. We're moving fast and shipping improvements weekly.
[Join our Discord β](https://discord.gg/Rammm3ts5u)
# Architecture
Source: https://docs.foenix.ai/core-concepts/architecture
How Foenix's multi-agent system processes your requests
Foenix is built as a **multi-agent system (MAS)** - four specialised agents work together, each with a narrow role. This is what makes Foenix able to run autonomously without losing control of the outcome.
## The two environments
Foenix has two parts that talk to each other over HTTPS:
**Foenix Cloud** - where the agents live. They reason about your request, plan steps, generate code, and verify results.
**Your WordPress site** - where the Foenix Connector plugin runs. It receives instructions from the Cloud, executes them on your server, and reports the result back. The Connector has admin-level access to WordPress but only acts on signed instructions from your account.
## The four agents
Every request goes through up to four agents. Simple requests use one or two; complex ones use all four with multiple iterations.
### Orchestrator - the lead
Receives your message, decides which execution path to take, and coordinates the other agents. It picks between paths depending on the request: a quick read-only answer, a single-step edit, a multi-step generation, an autonomous run, and so on.
On a heavy, long task the Orchestrator decomposes the request: it splits the task into parts and calls a dedicated Worker sub-agent for each one.
The Orchestrator is also responsible for the retry loop: if the Verifier returns a failure, the Orchestrator decides whether to try again with a new strategy or report the problem.
### Worker - the sub-agent
Used for heavy tasks. Every Worker gets its own slice of the job, researches the context it needs (theme structure, custom post types, existing plugins, ACF fields, taxonomies), and hands the Coder a precise, scoped instruction.
Because each part is handled by its own Worker, a ten-step task no longer depends on a single plan staying valid from step one to step ten. The result is noticeably higher accuracy and consistency on multi-step jobs.
### Coder - the executor
Translates the instruction into PHP and runs it on your WordPress server through the Connector. The Coder doesn't make decisions about *what* to do - only *how* to do it. This separation is deliberate: the agent that decides isn't the agent that executes.
The Coder reads freely but writes carefully. Every modification is wrapped in a transaction, logged before execution, and screened by the Safety Mode validator before it runs (see Safety Mode).
### Verifier - the checker
Read-only access to your site. After the Coder runs, the Verifier checks whether the result actually matches the original request - does the page render? does the plugin activate without errors? did the meta description get added? It returns a structured pass/fail verdict.
The Verifier checks whether the task was actually completed, not just whether the code ran. A plugin that activates but does nothing, or a page that renders but is missing the requested section, fails verification.
If it fails, the Orchestrator gets the verdict and retries with a corrected plan.
## How a request flows
You type a message, click an element, or a scheduled agent fires.
The Orchestrator picks an execution path based on the request type and your current Safety Mode.
For heavy tasks, the Orchestrator splits the request into parts and assigns each to a Worker sub-agent.
The Coder runs PHP operations on your server, one at a time, each with a transaction ID.
The Verifier checks the result. Pass β done. Fail β back to the Orchestrator for a retry.
You see the result in your session.
## Why multi-agent
A single LLM doing everything has two failure modes that matter at scale.
**It can't reliably check itself.** The same model that wrote the code is biased toward seeing it as correct.
**It can't recover from errors during long autonomous runs.** If a 10-step task fails on step 4, a single-agent system tends to either crash or hallucinate completion.
Splitting roles solves both. The Verifier doesn't share the Coder's blind spots. The Orchestrator can detect a failed verdict and decide what to do next without needing the original context that produced the error. And because heavy tasks are split across Workers, a failure in one part is isolated: the Orchestrator retries that part, not the whole task.
# Credits
Source: https://docs.foenix.ai/core-concepts/credits
How Foenix pricing works: credits, AI Modes (Lite, Plus, Ultra), plans, credit packs, and what real tasks cost.
Foenix uses a credit-based system. Every action your session performs consumes credits - reading data, writing code, generating images, searching the web, and running agents.
## Free credits
Every new account gets **500 free credits** - no credit card required. This is enough to explore all working modes and run several real tasks.
## What affects credit usage
Two main factors determine how many credits a task consumes:
**1. The AI Mode selected**
Every message runs in one of three modes. The mode sets the credit multiplier, and you can switch it per message right in the session composer:
| AI Mode | Multiplier | Best for |
| --------- | ---------- | ------------------------------------------------------------------------- |
| **Lite** | 0.3Γ | Light tasks at the lowest cost - scans, simple edits, routine content |
| **Plus** | 1Γ | The recommended default - balanced quality and speed for most tasks |
| **Ultra** | 3Γ | The strongest results - design work, strict content rules, complex builds |
A quick fix can run on Lite while a page build in the same session runs on Ultra - the mode applies to the message, not the whole session. Lite runs on a mix of fast, lightweight models; Plus and Ultra use larger, more capable models. Plus and Ultra are available on paid plans.
**2. The complexity of the task**
A simple question like "how many posts do I have?" has a small cost. A complex task - building a plugin, generating a full page, running a multi-step agent - consumes significantly more credits because it involves multiple AI calls, web searches, code execution, and file operations.
## What real tasks cost
Approximate costs from real runs, to give you a sense of scale:
| Task | Credits | AI Mode |
| --------------------------- | ------- | ------- |
| Blog post with images | \~198 | Plus |
| Broken links scan and fix | \~300 | Plus |
| Full site SEO audit and fix | \~400 | Ultra |
| Malware scan | \~86 | Lite |
| Monthly site health report | \~132 | Plus |
See the full breakdown on the [pricing page](https://foenix.ai/pricing).
## What else consumes credits
* **Cloud Sites** are billed daily while active (12 to 30 credits/day depending on size) - see [Quick Start](/get-started/quick-start) for tiers. Your free 24-hour demo site costs nothing.
* **Scheduled agents** consume credits on each run, at the same rates as running the task manually.
## Plans
| Plan | Credits | Sites |
| ----------------- | -------------- | ----------------- |
| Free | 500 one-time | 1 demo site (24h) |
| Starter - \$25/mo | 5,000 / month | 3 |
| Pro - \$50/mo | 10,000 / month | 25 |
Yearly billing saves 20%. Need more in a given month? On Starter and Pro, **credit packs** add 5,000 credits for \$19 without changing your plan. Full details on the [pricing page](https://foenix.ai/pricing).
## Tips to spend credits wisely
Ask for a report before asking for changes. "Find the problems, report only" costs little and shows you the scope - then "fix everything from the report" does the work with no wasted correction loops.
* **Be specific** - a clear, detailed instruction avoids back-and-forth correction loops that waste credits
* **Pick the right mode** - not every task needs Ultra. Routine content and scans work well on Lite or Plus
* **Test agents first** - run a task once manually before setting it as a recurring agent, so you know how much it costs in credits and how it performs
* **Match the prompt to the job** - big builds like a full homepage work fine as one prompt. For everything else, smaller steps are cheaper, easier to control, and simpler to verify
## Checking your balance
Your current credit balance is shown in the **bottom-left corner** of the Foenix dashboard.
## Running out of credits
* **Free plan** - credits do not refresh. Upgrade to a paid plan to continue
* **Starter / Pro** - credits refresh monthly. You can also purchase credit packs at any time without changing your plan
# How It Works
Source: https://docs.foenix.ai/core-concepts/how-it-works
How Foenix connects to WordPress, the agent pipeline behind every task, the four autonomy levels, and the safety layers around them.
Foenix connects to your WordPress site through a lightweight plugin and gives you a natural language interface to manage and edit your site.
## The two parts
**Foenix Cloud** - the Foenix platform where AI agents receive your instructions in natural language, analyse the task, build a plan, and execute it using various tools - web search, browser access, code execution, and more.
**Foenix Connector** - the plugin installed on your WordPress site. It is the bridge between your site and Foenix Cloud, communicating via the WP REST API. It reads your site content and applies changes.
## How a request works
1. You type a message in an open Foenix session
2. The **Orchestrator** analyses your request and your site's context, and routes the task
3. For heavy tasks the **Orchestrator** splits the work into parts and assigns each to a **Worker** sub-agent; the **Coder** executes step by step
4. The Connector deploys the changes on your WordPress site
5. The **Verifier** - a read-only agent - checks whether the task was actually completed, not just whether it ran. If verification fails, the task is retried with a different approach
The agent that decides is never the agent that executes, and the agent that executes is never the one that grades the work. That separation is what makes autonomy safe. [Architecture β](/core-concepts/architecture)
## Four levels of autonomy
From "nothing changes without me" to "runs while I sleep" - you pick the level per task:
Ask questions about your site - structure, content, code. Read-only: Foenix only reads your site content for these requests, no changes are made.
Click any element on your live site and describe the change. You point, the agent edits.
Describe a full task and Foenix modifies your WordPress site - new content, edits, plugins, snippets, and more.
Tasks that run automatically on a schedule - no chat open, no session running, no you.
Foenix has full administrator-level access to your WordPress site and can modify files, database, plugins, and themes. Before running any edits or agents on a real site, make a backup, or rehearse the task in a Cloud Site first. [Backups β](/security/backups)
## Safety modes
Foenix has 3 safety levels that control how strictly it validates actions before executing them. They work on top of the Verifier check that every change passes. In Soft mode the chance of something breaking is higher - always make a backup on your hosting before running any edits or agents. [Learn more β](/security/safety-mode)
## Data transfer security
All communication between Foenix Cloud and the Connector is encrypted over **HTTPS**. Every request is authenticated - no unauthenticated access to your site is possible.
If your firewall blocks incoming requests, switch the Connector to **pull-only mode** in its settings. The plugin then reaches out to Foenix Cloud itself, and no inbound connection to your server is needed.
## Abilities API
Coming soon. If enabled in your account settings, Foenix will first look for Abilities API capabilities registered on your site and use them to complete the task. If none are found, it falls back to the standard WP REST API.
# Sessions
Source: https://docs.foenix.ai/core-concepts/sessions
How sessions work in Foenix: starting, attaching context, AI Modes, stopping safely, history, and rollback.
A session is a conversation thread between you and your WordPress site. Each session has a title, a history of messages, and a record of all actions taken.
## Starting a session
1. Open your Foenix dashboard and click a connected site
2. Click **New Session** in the left sidebar
3. Type your first message Each session is tied to a single site. Sessions are kept separate per site.
## What you can attach
In any session you can attach additional context to your message:
* **Images** - screenshots, mockups, reference photos
* **PDF files** - documents, briefs, specifications
* **Text files** - any plain text content
* **ZIP archives** - upload a plugin or theme archive and Foenix unpacks it and reads the files inside
* **YouTube links** - Foenix can read and use video content
* **Any URL** - paste a link and Foenix will read the page
## Session duration
Depending on the task complexity and the selected AI Mode, a session can complete in seconds or run for several minutes. Simple queries respond instantly. Complex tasks - like building a plugin or a theme - may take longer. You can close the browser tab while a session is running - it will continue working in the background, and you get an email when the task finishes.
## Stopping a session
You can stop a session mid-run. The session keeps its context, so you can continue the conversation afterwards.
Credits already spent are not refunded, and stopping mid-run may leave your site in an incomplete state - for example a plugin half-installed or a file partially modified. Check the result before continuing.
## One task per session
We recommend creating a new session for each separate task. This keeps the context clean, reduces credit usage, and makes it easier to track what was done.
## Session history
All past sessions appear in the **Recent Sessions** list in the left sidebar, sorted by most recent. Click any session to reopen it - continue the conversation or review what was done.
## Context within a session
Foenix maintains context throughout a session. If you say "change the title of that post" after previously discussing a specific post, Foenix understands what you mean. Context does **not** carry over between chat sessions. Each new session starts fresh. Scheduled Agents are the exception: they keep a memory of your site between runs. [Scheduled Agents β](/working-modes/agents)
## AI Modes
Every message runs in one of three modes - **Lite** (0.3Γ), **Plus** (1Γ, recommended), or **Ultra** (3Γ). The mode sets the credit multiplier and the strength of the models behind it. Switch it per message right in the session composer: a quick fix can run on Lite while a page build in the same session runs on Ultra. Plus and Ultra are available on paid plans. [How modes affect cost β](/core-concepts/credits)
Behind every message, Foenix runs a pipeline of AI agents - Orchestrator, Worker, Coder, and Verifier - regardless of the mode you pick. The mode changes the horsepower, not the process. [How the pipeline works β](/core-concepts/architecture)
## SERP settings
If your task involves web search - for example writing an SEO article or researching competitors - Foenix uses the **SERP location and language** configured in **Settings - Personality**. Make sure these match your target market for best results.
## Rollback
After actions that modify your site, a **Rollback** button may appear in the session. If something could not be undone, Foenix tells you right away instead of reporting a false success. [Learn more β](/security/rollback)
## If something goes wrong
If you encounter errors or unexpected behaviour, reach out in our Discord community - the team responds quickly. [Join Discord β](https://discord.gg/Rammm3ts5u)
# Use Cases
Source: https://docs.foenix.ai/core-concepts/use-cases
Real prompts for Foenix agents with approximate costs: content, SEO, site health, builds, and WooCommerce automation.
Every example below is a complete, working prompt - paste it into a session as is, or adapt it to your site. Costs are approximate and depend on your site's size; the AI Mode listed is the recommended one for that task. [How credits and modes work β](/core-concepts/credits)
Tasks marked **scheduled** include a schedule right in the prompt and keep running on their own. The rest are one-time runs you trigger when needed.
## Content & SEO
### Autonomous blog Β· scheduled
A new article published every day: topic picked, text written, images generated, internal links added.
```text theme={null}
Every day write and publish a blog post relevant to my website's niche,
including 4 generated images: 1 featured image and 3 in-text body images.
Auto-link to related past posts.
```
\~198 credits per post Β· Lite
### SEO audit and fix Β· scheduled
Scans every post, fixes what can be fixed safely, and emails a report about the rest.
```text theme={null}
Audit SEO on all posts. Find broken links, missing meta descriptions,
missing alt texts. Fix everything and email me a report.
```
\~400 credits per run Β· Lite Β· works well weekly
### Make your site AI-ready
Prepares your site for AI crawlers: creates `llms.txt`, checks `robots.txt` rules, and reports what was changed.
```text theme={null}
Bring my site up to speed for AI crawlers: add an llms.txt with a summary
of the site and links to the most important pages, check robots.txt
for rules that block AI crawlers, and report what you changed.
```
Cost depends on site size Β· Lite
### Bulk content refresh
Old posts updated in one run: dates, outdated stats, new internal links, regenerated excerpts.
```text theme={null}
Update all posts older than 2 years: refresh dates, update outdated stats,
add new internal links, regenerate excerpts.
```
\~1,200 credits Β· Lite
### Broken links auto-fix Β· scheduled
Fixes what can be proven correct, quarantines the rest with suggestions.
```text theme={null}
Scan all internal and external links weekly. Quarantine 404s, suggest
replacements, fix automatically when confident.
```
\~300 credits per run Β· Lite
### Rank in Google Β· scheduled
Weekly top-10 analysis for your keyword, applied to your page, with a summary of what changed and why.
```text theme={null}
Every Wednesday, analyze the Google top-10 for my keyword, extract the SEO
patterns they share, compare against my page, apply the improvements,
and email me a summary.
```
\~350 credits per run Β· Lite
### SEO silo builder
A complete topical cluster: hub article, supporting spokes, and the linking structure between them.
```text theme={null}
Create Hub article (4000 words) + 5 supporting articles.
Internal Silo linking: HubβSpokesβsiblings.
```
\~2,300 credits Β· Lite
### Premium data content
A long-form hub with interactive charts built from real data, plus supporting articles.
```text theme={null}
Run keyword research. Build a long-form Hub with embedded interactive
charts from real data. 5 supporting articles, interlinked.
```
\~560 credits Β· Lite
## Site health
### Image optimization
The whole media library compressed and converted, with pages verified to render identically.
```text theme={null}
Compress all images in media library. Convert to WebP, add lazy loading,
generate srcset. Target Lighthouse > 95.
```
\~2,800 credits Β· Lite
### Malware scan
Every PHP file read in context, threats quarantined rather than deleted, exact paths reported.
```text theme={null}
Scan all PHP files for base64_decode, eval, hidden iframes.
Report with file paths. Quarantine confirmed threats.
```
\~86 credits Β· Lite Β· cheap enough to run daily
### Site health report Β· scheduled
A monthly PDF about uptime, vulnerabilities, updates and performance, delivered to your inbox.
```text theme={null}
Build a monthly site health report: uptime, vulnerabilities, updates,
performance. Generate PDF and email it.
```
\~132 credits per run Β· Lite
## Build
### Instant homepage
A rebuilt homepage tuned for speed, shipped as an isolated plugin so your theme stays untouched.
```text theme={null}
Build me a new homepage that loads instantly. Target Lighthouse 100.
```
\~3,700 credits Β· Lite
## WooCommerce
### Store-wide update with translations
Rebrand, reprice and translate an entire catalog in one pass.
```text theme={null}
Replace 'OldBrand' with 'NewBrand' across all products, raise prices 18%,
rewrite descriptions, translate DE/FR/ES.
```
\~1,200 credits Β· Lite
### Order alerts Β· event-triggered Β· coming soon
Event-triggered agents are in development. When they ship, this prompt will fire on every new order - no schedule, no open chat, no session running:
```text theme={null}
When a new WooCommerce order arrives, send instant Telegram notification
with order details and total.
```
Before scheduling any of these, run it once manually. You'll see exactly what it costs on your site and how it performs - then add the schedule line to the same prompt.
# What is Foenix.ai?
Source: https://docs.foenix.ai/get-started/introduction
AI agents that run your WordPress 24/7. Ask for something now, or set a task on a schedule: posts, pages, SEO fixes, site health.
Your WordPress, on autopilot. Foenix is a team of AI agents that lives inside your WordPress: it understands your site's structure, builds anything you describe, and keeps working when you close the tab. Ask for something now, or set a task that runs on a schedule. Foenix writes posts, builds pages and plugins, fixes SEO, and keeps your site healthy while you sleep.
Works with any WordPress: new or existing sites, any theme, any hosting. No migration needed.
## Four levels of autonomy
You decide how much to delegate, per task:
| Level | What it means | Docs |
| -------------------- | ----------------------------------------------------------------------------------------------------------- | ------------------------------------------- |
| **Live Chat** | Ask questions, analyze your site, get code answers. Nothing changes without you. | [Learn more β](/working-modes/live-chat) |
| **Click To Edit** | Point at an element, describe the change, watch it happen. | [Learn more β](/working-modes/vibe-coding) |
| **Build Mode** | Describe a full task. Foenix plans it, shows what it will change, and executes on your confirmation. | [Learn more β](/working-modes/direct-edits) |
| **Scheduled agents** | Tasks that run on their own: daily posts, weekly audits, monthly reports. No chat open, no session running. | [Learn more β](/working-modes/agents) |
Heavy tasks are split by the **Orchestrator** into parts, each handled by its own **Worker** sub-agent. Every change then goes through the **Verifier**, a read-only agent that checks whether the task was actually completed, not just whether it ran. If verification fails, the task is retried with a different approach. Learn how the pipeline works in [Architecture](/core-concepts/architecture).
Try Foenix in a Cloud Site in seconds, or connect your own WordPress in under 5 minutes
The four autonomy levels, safety modes, and what Foenix can touch on your site
Tasks that run automatically: publish articles, monitor site health, email reports while you sleep
Real prompts with real costs: SEO audits, autonomous blogs, WooCommerce automation, custom plugins, llms.txt
New here? The free plan includes 500 credits and a ready demo site, no card required. [Start free](https://foenix.ai/signup) or see [what credits buy](/core-concepts/credits).
# Quick Start
Source: https://docs.foenix.ai/get-started/quick-start
Spin up a Cloud Site or connect your own WordPress, and run your first AI task in minutes.
Foenix lets AI agents work on a WordPress site in two ways: a **Cloud Site** we host for you, or your **own self-hosted site**. New accounts get a free 24-hour demo site, so you can be running your first task in under a minute - no setup required.
## Step 1 - Create an account
Go to [foenix.ai/signup](https://foenix.ai/signup) and sign up. No credit card required - you get **500 free credits** and a **free 24-hour demo site** to explore immediately.
Your demo site is a fully-functional WordPress site deployed on our servers. It's the fastest way to get a feel for Foenix before connecting a real site. After 24 hours it's automatically removed, and you can launch a fresh one right from the dashboard whenever you need it.
## Step 2 - Choose where your agents work
In your Foenix dashboard, click **Add New Site**. You'll be asked where your agents should work.
Pick the path that fits you:
A persistent, fully-managed WordPress instance on our servers - **live in \~10 seconds**. Best for testing, demos, and learning the system without touching a production site.
Just signed up? Your free 24-hour demo site is already running - skip straight to **Step 3**. Deploy a persistent Cloud Site below only when you want one that lasts longer.
Click **Launch a Cloud Site**, then choose a storage size:
| Tier | Storage | Cost |
| ------------ | ------- | ---------------- |
| **Light** | 5 GB | 12 credits / day |
| **Standard** | 10 GB | 20 credits / day |
| **Heavy** | 25 GB | 30 credits / day |
Cloud Sites are **billed daily** for as long as they stay active. For example, a Light Cloud Site runs \~360 credits/mo. Click **Deploy** and your isolated WordPress instance is provisioned right away.
To move an existing WordPress site into a Cloud Site, or take your Cloud Site build out to your own hosting, use **WP Easy Migrate**. It comes preinstalled in every Cloud Site. [WP Easy Migrate β](/get-started/wp-easy-migrate)
Install the open-source Foenix Connector plugin on your real, self-hosted WordPress.
Foenix makes changes via the WordPress REST API. To stay safe, connect a hosting **staging environment** (Kinsta, WP Engine) or install a **backup plugin** (e.g. UpdraftPlus) before running any agents. [Learn more β](/security/backups)
On the connection screen, click **Download Plugin**, or grab it directly:
Latest version - install via WordPress admin
Do not unzip the file - WordPress installs it directly from the archive.
1. Go to **Plugins β Add New β Upload Plugin**
2. Choose the `.zip` file you just downloaded
3. Click **Install Now**, then **Activate**
In your WordPress admin sidebar, open **Foenix.ai** settings and click **Connect Account**.
You'll be redirected back to Foenix automatically - your site will appear as **Connected** in the dashboard.
Behind a firewall that blocks incoming requests? Switch the Connector to **pull-only mode** in its settings. Foenix will then reach your site without any inbound connection.
## Step 3 - Run your first task
Click your Cloud Site or connected site in the Foenix dashboard to open a new session. Start with a question - questions are read-only and cost almost nothing:
```text theme={null}
How many published posts do I have?
```
Then give the agent a real job. Asking for a report first is a good habit: you see what Foenix found before anything changes.
```text theme={null}
Find broken links and missing meta descriptions across my posts.
Report only - don't change anything yet.
```
When the report looks right, reply with one more line and the agent does the work:
```text theme={null}
Fix everything from the report.
```
Working against a real site? Before making any edits or running agents, make a full backup, or rehearse the task in a Cloud Site first. [Learn more β](/security/backups)
## What's next
The four autonomy levels and what Foenix can touch on your site
Put a task on a schedule and let it run without you
What tasks cost and how Lite, Plus and Ultra modes change the price
# WP Easy Migrate
Source: https://docs.foenix.ai/get-started/wp-easy-migrate
Move your WordPress site between a Foenix Cloud Site and your own hosting in two clicks: create a backup on one site, import it on the other. URLs and the database are adapted automatically.
WP Easy Migrate is a one-click migration plugin built by Foenix. It packs your whole site - database, media, plugins, and themes - into a **single `.zip` file** that you can download and import on any other WordPress site with the plugin installed.
It's built for moving sites in any direction:
* **Cloud Site β your own hosting**: built something in a Cloud Site and want it live? Move it to your real site.
* **Your hosting β Cloud Site**: clone your live site into a Cloud Site to let Foenix agents experiment safely.
* **Site β site**: works between any two WordPress sites, not just Foenix ones.
Cloud Sites run on **SQLite**, while most hosting uses **MySQL** or **MariaDB**. You don't have to think about this: the database is converted automatically during import (MySQL β MariaDB β SQLite). The plugin also **rewrites the site URL** and adapts the database to the new server for you.
## Before you start
Install and activate WP Easy Migrate on **both** sites - the one you're copying *from* and the one you're copying *to*. Every Cloud Site comes with it preinstalled, so you only need to install it on your own hosting. After activation, it appears in the WordPress admin sidebar as **WP Easy Migrate**.
Latest version - install via **Plugins β Add New β Upload Plugin**
Do not unzip the file - WordPress installs it directly from the archive.
At the top of the plugin screen you'll always see where you are: the current site URL, the database type (for example `SQLITE`), and the table prefix. Double-check this line before importing so you don't overwrite the wrong site.
## Step 1 - Create a backup (source site)
Open **WP Easy Migrate β 1. Create backup** on the site you want to copy.
Choose what goes into the backup:
* **Media files** - check *Include the uploads folder (media library)* to bundle your images and uploads. Uncheck it if you only need content and settings (the backup will be much smaller).
* **Database** - always included. No configuration needed; conversion between database engines happens automatically on import.
* **Plugins** - tick the plugins you want to carry over, or use **toggle all**.
* **Themes** - same for themes.
Click **Create backup**. A progress bar shows what the plugin is doing (for example, *Scanning plugin: wp-easy-migrate*). You can safely hit **Cancel** at any point - creating a backup never changes your site.
When it's done, you'll see a green **Done!** box with the file name and size:
Click **β Download backup** to save the `.zip` to your computer.
Backup file names include the site and timestamp, like `wpem-backup-yoursite-20260717-115030-β¦.zip`, so you can always tell which backup came from where.
## Step 2 - Import on the destination site
On the site you're moving *to*, open **WP Easy Migrate β 2. Migrate (import)**.
Under **Or upload a backup from another site**, choose the `.zip` you downloaded and click **Upload and analyze file**. A progress bar shows the upload speed and time remaining - you can **Cancel** at any point.
Uploading and analyzing a backup is **safe** - nothing on the site changes yet. The plugin only shows you what's inside. The database and selected files are replaced **only after** you review the backup and explicitly click **Import and migrate**.
### Review what will be migrated
Once the file is analyzed, the plugin shows a **What will be migrated** summary:
* **Site URL** - the backup's URL will be replaced with this site's address automatically, across the whole database.
* **Database** - source β destination engine (for example `MYSQL β SQLITE`). Conversion is automatic; the database name comes from the current site's `wp-config`.
* **Source table prefix** - adapted to the current site for you.
Then choose what to restore:
* **Plugins and themes in the backup** - untick anything you don't want on this site.
* **Restore media files (uploads)** - bring over the media library.
* **Keep the current site's users and login** - recommended: you stay logged in after the import instead of being logged out.
* **Safe mode: do not auto-activate plugins after import** - recommended: guarantees the site opens after migration. You turn plugins on yourself in the **Plugins** screen afterwards.
**Only import backups you created or fully trust.** An import restores a database and PHP files from the archive and runs them on this site. A backup from an untrusted source could contain malicious code. Keep *Safe mode* on when in doubt.
Click **Import and migrate**. When the import finishes, log in to the destination site and check that everything looks right. If you kept Safe mode on, go to **Plugins** and activate the ones you need.
Backups created on this same site appear under **Backups on this site** with a **Restore** button - you can roll the site back to an earlier state without uploading anything.
Importing **replaces** the destination site's database and the selected files. If the destination site has content you care about, create its own backup first - it takes one click on the *Create backup* tab.
## No upload or size limits to worry about
Big site? Not a problem:
* **Uploads are chunked.** Large backup files are uploaded in small pieces (around 10 MB per chunk, adjusted per server), so your host's `upload_max_filesize` limit doesn't apply.
* **Imports are resumable.** The import runs in small steps, so it won't die on servers with short PHP execution limits - and it does not touch the live site until the final, atomic switch.
## FAQ
Yes. Create the backup with WP Easy Migrate on the source site, and import it with WP Easy Migrate on the destination site. Cloud Sites have it preinstalled. Backups made by other tools won't work here.
No - this is exactly what the plugin was built for. The database is converted automatically on import, in either direction. You don't need to export SQL dumps or configure anything.
Yes. Uploading and analyzing a backup changes nothing. The site is only modified after you click **Import and migrate**.
With Safe mode on, plugins from the backup are copied to the site but **not activated** automatically. This guarantees the site opens after migration even if one of the plugins would crash on the new server. You then activate them one by one in the **Plugins** screen.
Yes - uncheck *Include the uploads folder* to skip the media library, and untick plugins or themes you don't need on the destination. The database is always included.
Spin up a Cloud Site or connect your own WordPress in minutes
Why you should back up before big changes, and how Foenix handles safety
# Backups
Source: https://docs.foenix.ai/security/backups
Backups. Backups. Backups. This is the most important habit when using Foenix. Make a backup before every session where you plan to make changes. No exceptions.
## Why backups are critical
Foenix has full administrator-level access to your WordPress site and can modify files, the database, plugins, and themes. If something goes wrong - an unexpected conflict, a PHP error in generated code, or an incomplete agent run - the fastest recovery path is always a recent backup. Foenix has a Rollback feature, and it tells you honestly when something could not be undone, but it does not cover everything - especially settings and options. [Rollback β](/security/rollback)
## Where to make backups
**Always back up at the hosting level - not inside WordPress.** A backup plugin inside WordPress only protects you if WordPress itself is still running. If the site breaks completely, you need a backup that exists outside of it - on your hosting server or in cloud storage. Most hosting providers offer:
* Automatic daily snapshots (cPanel, Plesk, Cloudways, etc.)
* One-click restore from the hosting control panel Check your hosting dashboard and enable automatic backups if not already active. If your hosting doesn't provide snapshots, use a backup plugin that stores copies **outside your site** - for example UpdraftPlus or BlogVault with cloud storage. The rule stays the same: the backup must survive even if the site doesn't.
## Cloud Site and staging
The safest way to try a risky or bulk task is a **Cloud Site**: a WordPress instance on our servers where you can rehearse the task before running it on your live site. [Quick Start β](/get-started/quick-start)
To rehearse on a copy of your real site, move it into a Cloud Site with **WP Easy Migrate**. It packs your whole site into a single backup file and imports it on the other side, with URLs and the database adapted automatically. [WP Easy Migrate β](/get-started/wp-easy-migrate)
For changes on a live site, **please rely on backups at the hosting level**.
## When to make a backup
* Before any session where you plan to make edits
* Before running an agent for the first time
* Before modifying `functions.php` or theme files
* Before installing or modifying plugins
# Rollback
Source: https://docs.foenix.ai/security/rollback
Rollback lets you undo changes made by Foenix.
Every WordPress stack is different, and rollback coverage is extended to new configurations with every release. When something cannot be undone, Foenix tells you right away instead of reporting a false success. Rollback is a safety net, not a backup: always keep one at the hosting level. [Backups β](/security/backups)
## How rollback works
Before Foenix modifies your site, the previous state is saved. If the change causes an error, Foenix detects the problem and reverts to the saved version automatically. You can also trigger a rollback yourself from the **Rollback** button in the session.
## Honest by design
After a rollback, the session reports exactly what was reverted and what was not. If a change could not be undone, you see it immediately in the session and can act on it, instead of discovering it later.
## What rollback covers
* File changes: theme files, plugin files, snippets
* Post and page content, including long posts with images and SEO meta
## Limitations
* Settings and options changes are not reversible via rollback
* If the site is completely broken and the dashboard is inaccessible, rollback cannot help - restore from a hosting backup instead
## If something goes wrong
Contact support in Discord - the team responds quickly. Share your session ID so we can help faster.
[Join Discord β](https://discord.gg/Rammm3ts5u)
# Scheduled Agents
Source: https://docs.foenix.ai/working-modes/agents
Autonomous tasks that run on a schedule or on site events: creating, testing, and managing Foenix agents.
Agents are autonomous tasks that run on a schedule - daily, weekly, monthly, or at a custom interval - without you being present. Describe the task once, set the schedule, and Foenix handles the rest.
## What agents can do
* Automatically research fresh news and publish SEO-optimised articles
* Monitor site health and log errors
* Generate and set featured images
* Check for missing meta descriptions
* Send weekly reports to Telegram - ask in chat how to set this up
* Run any recurring task you would otherwise do manually
## Two ways to create an agent
**Way 1 - From a session**
Type your task in a new session in plain language. Foenix will interpret it, expand it into a full detailed prompt, and show you a **Schedule Task** card with the exact steps and timing. Click **Create** to save it.
```text theme={null}
Every Monday at 9am - research trending topics in [your niche],
find relevant keywords, write an SEO-optimised article,
generate a featured image, and publish it.
```
Foenix will automatically expand this into a detailed structured prompt and set the schedule. An agent created from a session inherits that session's AI Mode: start in Lite, and the agent runs in Lite too.
**Way 2 - From the Agents page**
Click **New Agent** in the top right corner of the Agents page. You will be asked how you want to build it: through a chat, where Foenix expands your description into a full prompt, or by filling in the form yourself:
* **Name** - e.g. "Daily new post"
* **Prompt** - describe what you want the automation to do
* **AI Mode** - Lite, Plus, or Ultra
* **Safety mode** - select the safety level
* **Schedule** - Interval, Daily, Weekly, Monthly, or Custom
Then click **Create**.
## Managing agents
Go to **Agents** in the left sidebar to see all agents for the current site. Each agent card shows the prompt preview, schedule, and last run date.
| Action | What it does |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------- |
| **Edit** | Change the prompt, AI Mode, safety mode, or schedule |
| **Run Now** | Run the agent once immediately and open the created session |
| **Pause / Resume** | Pause the schedule without deleting. Sessions already running, including ones started with Run Now, continue to completion |
| **Delete** | Permanently remove the agent |
## Always test first
Before setting a recurring schedule, click **Run Now** to run the agent once. Check the output, verify it looks correct, and see how many credits it consumes - then activate the schedule.
## Memory and follow-ups
Scheduled Agents keep a memory of your site between runs, so a weekly audit does not rediscover your setup every Monday.
A finished agent session can be continued: open it and write a message, and the agent picks up where it stopped.
## Writing good agent prompts
The more specific your prompt, the better the result. You can write in plain language and Foenix will interpret it - or write a detailed step-by-step prompt directly:
```text theme={null}
1. Search the web for trending topics in [your niche] this week
2. Pick the best keyword based on search volume
3. Write a 800-1000 word SEO article in [language]
4. Generate a relevant featured image
5. Publish with title, meta description, and the image
```
## Safety mode for agents
Each agent has its own Safety Mode setting. Please set this at your own discretion and risk. [Learn more β](/security/safety-mode)
Always make a backup before running agents on a production site. Agents can modify content, files, and settings automatically. [Backups β](/security/backups)
# Build Mode
Source: https://docs.foenix.ai/working-modes/direct-edits
How Foenix executes full tasks on your WordPress site: content, theme files, plugins, snippets, and settings - with verification on every change.
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 β](/core-concepts/architecture)
## 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 β](/security/backups)
## Example
You say:
```text theme={null}
Add a "Back to top" button that appears when the user
scrolls down 300px. Match the site's primary color.
```
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 β](/core-concepts/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 β](/security/rollback)
## 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 β](/security/safety-mode)
Always make a backup before running edits on a production site, or rehearse the task in a Cloud Site first. [Backups β](/security/backups)
# Live Chat
Source: https://docs.foenix.ai/working-modes/live-chat
The conversational, read-only mode of Foenix: ask anything about your WordPress site's content, structure, and code.
Chat (also known as Live Chat) is the conversational mode of Foenix. Ask anything about your WordPress site and get instant answers - no changes are made to your site in this mode, and read-only questions cost very few credits.
## What you can ask
**About content**
```text theme={null}
How many published posts do I have?
Show me all posts in the "News" category.
Which posts are missing a featured image?
Which posts have no meta description?
```
**About structure and code**
```text theme={null}
Where is the contact form submission handled?
What plugins do I have installed and active?
How is my main menu structured?
What custom post types are registered on my site?
What hooks does my theme use?
```
**Site audit**
```text theme={null}
Which plugins haven't been updated in over 6 months?
Are there any posts with duplicate titles?
Show me all pages that have no content.
Which images in the media library are not used anywhere?
```
## Tips for better results
**Be specific about what you need:**
```text theme={null}
// Less effective
Tell me about my posts
// More effective
Show me the 5 most recent published posts
with their titles, dates, and word counts
```
**Use it to plan before you build:**
```text theme={null}
I want to add a "Team Members" section with name, role, and photo.
What files would need to be created or modified?
```
**Ask follow-up questions:**
```text theme={null}
You mentioned the contact form is in contact.php -
can you show me the validation logic?
```
## From chat to action
When you're ready to make changes, just say so in the same session:
* *"Do it"* or *"Apply this"* - Foenix switches to [Build](/working-modes/direct-edits) and applies the change
* Switch to [Click-to-edit](/working-modes/vibe-coding) to click and edit any element visually
* Say *"Set this up as a weekly agent"* to automate the task on a schedule - see [Scheduled Agents](/working-modes/agents)
# Click to Edit
Source: https://docs.foenix.ai/working-modes/vibe-coding
Visual editing mode: click any element on your live site, describe the change, and Foenix applies it to the exact file responsible.
Click-to-edit is a visual editing mode. Instead of describing where something is, you point at it - then describe what you want to change.
## How it works
1. Open a session and click **Live** in the bottom toolbar
2. Your live site appears in the center panel, with the current page URL shown above it
3. Click **Visual Edit** and select any element - text, image, button, heading, section
4. The selected element is highlighted with an orange dashed border
5. Describe the change in the text field on the right
6. Foenix finds the exact file responsible and applies the change
## What you can edit
| Element | What you can change |
| --------------- | -------------------------------------------- |
| Text / heading | Content, font size, color, weight, alignment |
| Image | Replace image, change alt text, adjust size |
| Button | Label, color, border radius, link target |
| Navigation item | Label, URL, visibility |
| Section / block | Layout, background, spacing, visibility |
## Example prompts
```text theme={null}
Change this heading to "Welcome to Pizza School Dubai"
```
```text theme={null}
Make this button larger and change the label to "Book a class"
```
```text theme={null}
Replace this image with a food photography style banner - warm tones
```
```text theme={null}
Hide this section on mobile devices only
```
## Tips
* You can switch between Live and the chat panel at any time in the same session
* Links to your site's pages in session results open right in Live mode
* If you select the wrong element, click elsewhere to deselect and try again
* For changes affecting multiple elements at once, use [Build](/working-modes/direct-edits) instead
* Works with both classic themes and block (FSE) themes
Always make a backup before making changes on a production site. [Backups β](/security/backups)