FAQ
Questions, answered
What people ask before they install NiroCoder, credits, safety, what it can build, where the code lives and what leaves your site.
Getting started
The plugin is free. The AI service it needs starts with a free trial: 7 days and 50 credits, whichever runs out first. No card required. After that, a yearly license, or a lifetime license with 3 years of AI credits gives you AI credits and export. Lifetime credits are not unlimited. Running what you built never costs a credit.
Building, changes, fixes and answers pause, and NiroCoder offers an upgrade. Every extension you already built keeps running on your site. Export as a plugin is part of the paid plans.
No. NiroCoder connects to its own AI service. You connect your site with your name and email, paste the key from the verification email, and start building.
No. You describe what you need and review a plain-language plan. If you do code, every extension is readable PHP in its own folder that you can inspect.
Small, well-defined features: custom post types and catalogs, WooCommerce order statuses and checkout rules, admin tools, access rules, automations and shortcodes. Each one is an extension you can turn on, change, undo or remove.
PHP 7.4 or later. The admin app needs WordPress 6.6 or later; the plugin is tested up to the version in its readme.
Go to NiroCoder → Settings → AI Connectivity, enter your name and email, tick the data-sharing notice and click Send code. Paste the key from the verification email and your free trial starts. It takes about a minute.
Administrators, users with the manage_options capability. NiroCoder’s menu and its REST API are not available to other roles.
Credits & plans
AI requests only: chat messages, plans, builds, changes and “Fix with AI”. A plan or a question is 1 credit and a build or change is 5 (the defaults), so a planned-and-built feature is about 6. Turning extensions on or off, undoing an update, removing an extension, exporting it, and running extensions on your site never use credits. A request that fails is not charged.
You get 7 days and 50 credits, starting when you verify your site. The trial ends when the days or the credits run out, whichever comes first. It is one trial per account, not per site, and it does not refill.
Building and answering pause until you upgrade (on the trial) or until the next monthly release (on a paid plan). Top-up packs are coming soon. Every extension you already built keeps running.
No. Connect your site with your name and email, paste the key from the verification email, and the trial starts. Connecting takes about a minute.
Export as a plugin is part of the paid plans. On the trial you can build, run and change extensions, but not download them as a standalone plugin. Exporting itself never uses credits.
Credits are one pool for your account, shared by every site you connect, and the balance on each site shows the shared total. Plans are sold for 1, 5 or 25 sites.
Yearly credits are released monthly. Credits you do not use in a month do not carry forward. Top-up packs are coming soon. They are not for sale yet.
Not yet. Top-up packs are coming soon. The prices are on the pricing page, and there is no way to buy them until they launch.
A lifetime license covers the plugin, updates, and the extensions you build. AI credits are not unlimited. They are released monthly for 3 years: 25 a month on Starter (900 in all), 125 a month on Pro (4,500 in all), 333 a month on Agency (about 12,000 in all). After those 3 years, extra credits come from top-up packs, which are coming soon.
A canceled yearly plan keeps its monthly credit releases until the end of the license year you paid for. After that, building pauses and your extensions keep running.
Settings → Usage lists every AI request, newest first, with what it was and the credits it used. Requests that failed show the reason and “Not charged”.
No. Stopping a build cancels it on your site, but the credits for that build are already used.
Yes. It is a new build, so it uses build credits again, just like the first one.
Building
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.
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.
Yes. Open it and choose Change with AI, then describe what you want. You get an update plan to approve, and the latest update can be undone in one click.
Yes. With every request it sends a site summary that includes whether WooCommerce is active, its version and whether HPOS is on, so the plan fits your store. Orders and customer data are never sent.
Yes. NiroCoder knows whether WooCommerce is active and can build order statuses, checkout rules, product visibility and order automations. Plans the AI flags as high risk, anything touching payments, for example, need your explicit confirmation.
Yes, on different extensions. Each extension is locked while it is being built, undone or removed, so two administrators cannot change the same one at once.
Safety
Yes. The AI service reviews it, and NiroCoder runs its own local check on your server, syntax, a list of dangerous functions, file access, network calls and option changes, before a build can be activated. Blocked builds never reach your site.
NiroCoder turns it off automatically after the first fatal error and shows what happened, with “Fix with AI” and “Undo last update”. As a last resort, add define( 'NIROCODER_DISABLE_EXTENSIONS', true ); to wp-config.php to stop every extension from loading.
No. It is a static review of the code before it runs: it blocks known-dangerous functions, file and network access patterns and sensitive option changes. Extensions then run with normal plugin permissions, which is why every build starts from a plan you approve.
Nothing on your site changes. NiroCoder shows each blocked finding with its file, line and reason, and offers Fix and rebuild, which sends the plan back with those findings as instructions.
When you turn an extension on, NiroCoder first loads WordPress with only that extension in a separate PHP process, with a 128 MB memory limit and a 25-second time limit. If it crashes there, it is not turned on and your site is not affected. If your host cannot run the test, activation goes ahead and crash detection is the safety net.
No extension loads until you resume. Each extension keeps its status, so resuming brings back exactly what was on. Pausing and resuming are recorded in the activity log.
Your extensions
No. Extensions are loaded by NiroCoder, so they stop while it is deactivated. Nothing is deleted: reactivate the plugin and they run again. To keep a feature without NiroCoder, export it as a normal plugin .zip (a paid-plan feature), it runs on its own, but without the safety net (no crash protection, undo or activity log), and exports are provided as is.
Undo reverts the latest update, in one click. Every version is kept on disk under the extension’s history/ folder, but picking an older one from the screen is not available yet.
Deleting the plugin removes its settings, chat history and every generated extension in wp-content/nirocoder/. Deactivating keeps everything. Export (a paid-plan feature) any extension you want to keep before you delete NiroCoder.
No. Undo puts the code back to the version before the latest update. Posts, terms, orders and other data you added are kept.
Not from the screen. Removing moves the code to wp-content/nirocoder/trash/, where it stays until you uninstall NiroCoder, and deletes the extension’s private settings. Content it created is kept.
In wp-content/nirocoder/extensions/<slug>/, one folder per extension, with every version kept under history/. NiroCoder loads active extensions on every request; they are not separate plugins, but paid plans can export any of them as a standalone plugin zip.
For features you would otherwise search for a snippet to do, yes: NiroCoder writes the code for your site, shows a plan first, checks it before it runs and manages it as an extension. If you already have a snippet you trust, a snippet plugin is a fine place for it.
Privacy & data
Your messages and recent conversation, a summary of your setup (versions, theme, plugins, WooCommerce status, your NiroCoder extensions), four diagnostics with chat messages, and, when changing or fixing an extension, that extension’s files and last error. Posts, pages, orders, customers and users are never sent.
Nothing goes to the AI service until an administrator connects the site in Settings → AI Connectivity and agrees to the data-sharing notice. The one exception is the plugin’s update check, which asks my.nirosuite.com for the latest NiroCoder version a couple of times a day and, like every WordPress update check, identifies your site’s URL.
There are none to store. NiroCoder uses its own AI service, authenticated by a per-site key, no OpenAI, Anthropic or other third-party key.
No. Extensions run on your own server, and running one never contacts the AI service; NiroCoder talks to it only when you chat, build or check your plan and credits. An extension you built to send data somewhere, such as a CRM sync, says so in its plan’s “Will create” list.
Every request to the service. The site key is removed from your site and the site is deregistered on the service. Your extensions, conversations and settings stay on your site, and your name and email are remembered for a quick reconnect.
Still deciding? Try it on a staging site
The plugin is free, the trial needs no card, connecting takes a minute, and nothing is built until you approve a plan.