See exactly what it will do, and what it won’t, before it does anything
Every request becomes a plan first: what NiroCoder understood, what it will create, what it will change, what it won’t touch, and a risk level with the reason. Nothing is built until you say yes.
What I understood
Your request restated in plain language, so a misunderstanding shows up before any code exists.
Will create · Will change
Everything the extension adds to your site, and anything existing it alters, listed separately.
Won’t touch
What stays as it is, your theme, your content, other plugins. Stated up front, not implied.
Risk with a reason
Low, medium or high, with one line explaining why, so you know what you are approving at a glance.
Needs
Plugins, settings or information the feature depends on, flagged “not found on this site” when they are missing.
Change the plan
Not quite right? Reply in the chat and get a revised plan. A newer plan replaces the old one, so you never approve a stale version.
Approval rules
You decide how much each risk level needs
Settings → General sets the approval rules. Defaults are careful; the high-risk gate cannot be turned off.
- Low risk: one approval (“Build it”), or let low-risk plans build automatically
- Medium risk: “Will change” is shown before you approve, by default
- High risk: an explicit “I understand this changes how my site works” checkbox, always on
- A new extension never turns itself on, activating it is always your click
Enforced, not just shown
The high-risk confirmation is checked on the server
Plans the AI service flags as high risk, anything touching payments or login, for example, need the confirmation box. The plugin refuses to start the build without it, even if someone calls the REST API directly.
- Server-side check, not only a disabled button
- Approved plans record who approved them and when
- A reloaded chat shows what was approved, by whom
- “Fix and rebuild” of a high-risk plan carries the confirmation forward
The details
- Plan fields
- Name, type, risk, what I understood, will create, will change, won’t touch, needs, optional alternative, why this risk level
- Risk levels
- Low, medium, high, set by the AI service’s plan, with a one-line reason
- Plan actions
- Build it (or Apply update) · Change plan · Cancel (or Discard)
- Plan states
- Pending → approved, canceled or superseded by a newer plan in the same chat
- Low-risk auto-build
- Off by default. Activating a new extension stays manual either way
- High-risk confirmation
- Always required; enforced on the server
- Dependencies
- Activation is refused while a required plugin (WooCommerce today) is inactive
Questions
No build starts without an approved plan. By default every plan needs your approval; you can let low-risk plans build automatically, but turning a new extension on is always a separate step you take. An update to an extension that is already on goes live once its plan is approved and the build passes the check. High-risk plans always need an explicit confirmation.
The AI service assigns it in the plan, with a one-line reason. The plugin enforces the approval rule for whatever level the plan carries, and separately, the local security check blocks dangerous code regardless of the label.
Choose “Change plan” and reply in the chat. NiroCoder returns a revised plan, and the older one is marked superseded so it can no longer be approved.
What NiroCoder understood, what it will create, what it will change, what it won’t touch, what it needs, the risk level with a one-line reason, and sometimes an alternative. Nothing is built until you approve it.
The plan lists it under Needs and marks it “not found on this site”. An extension that depends on WooCommerce will not turn on while WooCommerce is inactive.
A plan is 1 credit, like any chat message. Building it is 5 more (the defaults). Asking for a revised plan is another message; cancelling one is free.
Describe it. Review the plan. Ship it.
Install the plugin, connect with your email, and see your first plan in a couple of minutes.