Ask AI

Say who should see which widget, in your own words. Ask AI asks about anything it can't decide safely, drafts the rules, tests them against sample visitors, and shows you the plan. Apply puts it in the editor, marked and unsaved. Save is still yours.

What you can do

You already built the homepage hero ruleset in Widget Selection Rulesets: a spring sale rule, a German rule, a Pro rule, and a default. Ask AI is a second way to change it. Say who should see which widget, in your own words, and it writes the rules.

Three everyday jobs:

Run a sale for a month. Type “Show the holiday sale widget from December 1 to December 31, and the default otherwise.” Ask AI adds one rule on the current time, in your time zone, that stops matching on its own after December 31.
Target a section of the site. Type “If the URL path contains /pricing, show the pricing promo.” Ask AI adds a path parameter and a condition that ignores case, and tells you your app now has to send path.
Change a rule you already have. Type “Pro and enterprise customers see the upgrade offer.” Your Pro rule already points at the Pro hero, so Ask AI asks whether to replace it or keep both before it writes anything.

Ask AI only builds rules. It picks from widgets that already exist in this environment, and it never saves or publishes. Your visitors see a change when you Save on Development, or when you publish on Staging and Production.

How Ask AI thinks

Ask AI proposes; you decide. It never changes the editor by itself. It answers with a plan: the changes in words, the visitors it tested, and what your app needs to send. Apply puts the plan into the editor, marked and still unsaved. Save is yours.

It tests before it shows you. Ask AI makes up visitors — for the holiday sale, one on December 15 and one on January 2 — and runs each through the proposed rules with the same engine that serves your site. The plan lists which widget each one got.

It asks when a wrong guess would change what visitors see:

which widget you mean, when a name fits several or none;
a date window that has already ended, or a date that reads two ways, such as 04/05;
whether to replace or keep rules your request overlaps;
which widget wins when two groups overlap — what does a Pro visitor from the US see, if Pro visitors see one widget and US visitors another?
the values themselves, when you mention a list without giving it.

It decides the rest itself: rule labels, parameter names, ignoring case for paths and campaigns. You can change any of that by asking, or in the editor after you apply.

Times are in your time zone. Ask AI reads “December 1” in your browser's time zone and names the zone in its reply. Say so if you mean another one: “from 9 AM London time.”

Ask your first change

You need Widget Selection Access (Manage or Admin) for the environment, and Composer Ai Editor under Widget Access — the same grant that turns on Ask AI in the composer.

Open the organization → team → project → environment. Find the orange Widget Selection Rulesets card and open the homepage hero ruleset. On Manage Ruleset, click Edit Ruleset.
The Ask AI panel sits beside the rules, or above them on a narrow screen. Close it and an Ask AI button waits in the lower-right corner of the screen, wherever you have scrolled; click it to bring the panel back. The editor remembers whether you left the panel open.
Type “Show the holiday sale widget from December 1 to December 31, and the default otherwise”, or click an example to put it in the box, and press Enter. Shift+Enter starts a new line. While Ask AI works, Send becomes Stop.
If Ask AI asks a question, answer it in the same box. Answering is free.
Read the plan under the reply. Not applied yet means exactly that. Check the changes, open the tested visitors, and read What your app sends.
Want it different? Say so — “end it on the 24th” — and Ask AI revises the plan. That is free too, while the plan is waiting.
Click Apply. The new and changed rules are marked Added by AI or Changed by AI, and the panel says the changes are not saved yet.
Look them over, Dry run if you like, then Save. On Staging or Production, publish from Manage Ruleset when you are ready, the same as always.

Discard drops the plan and leaves the rules as they were. Start over (the circular arrow in the panel header) clears the conversation.

Reading a plan

Part of the plan	What it tells you
Changes	Each change in words: a rule added, a condition changed, a parameter added. No changes to the rules means Ask AI only answered.
Tested with 3 visitors: all see the right widget	The made-up visitors and the widget each one got. Open it to see them. When a visitor gets the wrong widget, it reads 1 of 3 checks failed instead and opens by itself.
Lines with a warning sign	Things worth a look before you apply: a widget that is not published in this environment yet, a rule that an earlier rule always beats, a date window that is already over.
What your app sends	Every field the rules read, with its type and an example. When a plan adds a field, your app has to start sending it, or those rules never match.
Code for your app	The same fields as code to copy: React, and JSON params for an HTTP call or the HTML embed. See Resolve from your app.

Edit the rules while a plan is waiting, and it can no longer be applied. The plan was tested against the rules as they were. Undo your edits, or ask for an updated plan.

What Ask AI will not do

When you ask for one of these, Ask AI says why in a sentence and offers the workaround as a question. It builds the workaround only if you say yes.

Request	Why it does not work directly	Do this instead
“Show widget A to half the visitors” / an A/B test / random rotation	Rules do not pick at random, so a visitor sees the same widget on every visit.	Have your app send a stable number from 0 to 99, such as a hash of the user id. Ask AI then writes “under 50 sees A, the rest see B.”
“Visitors from Germany” / “on mobile”	RuleCMS only knows what your app sends. It does not detect location, device, or browser.	Have your app send `country` or `device`. Ask AI adds the parameter and lists it in What your app sends.
A list of more than 64 values	One condition holds at most 64 values.	Have your app send a group, such as `segment` set to `vip`, and match that.
“Visitors who have seen this before” / “who clicked”	RuleCMS does not remember visitors.	Have your app send a flag or a count.
Create or edit a widget	Ask AI chooses among widgets that already exist in this environment.	Build the widget in Widgets first, then ask.
Publish, promote, or copy the ruleset	Publishing is a separate, explicit step. Ask AI only changes the draft in the editor.	Use Manage Ruleset. See Publish, promote, and history.
Change another ruleset, or another environment	Ask AI only sees the ruleset you have open, in the environment you are in.	Open that ruleset and ask there.

Credits and usage

One request is one credit. It is spent when the request starts. Failed and stopped requests still count.
Follow-ups are free. Answering Ask AI's questions, and asking for changes to a plan that is still waiting, continue the same request. You can tell by the message box: it reads Reply, or ask for a change to the plan…
Otherwise a message starts a new request. That includes your next message after Apply, Discard, Stop, or Start over.
The credits are shared with the composer. Ask AI in the composer spends the same credits, from the team's Ask AI billing page — a separate bill from the RuleCMS plan. When the team is out of credits, a dialog points you there.
Usage shows rulesets by name. The team's AI Usage tab lists each ruleset and widget that used credits, with its type, this month's and all-time credits, and failed requests. It is there for people with View Analytics.

When you will not see Ask AI

The Ask AI panel and its button are hidden, not disabled, when Ask AI cannot work for you:

You can view the ruleset but not edit it. Ask AI needs Widget Selection Access Manage or Admin for the environment.
Your team has not granted you Composer Ai Editor under Widget Access for the environment. Staging and Production have their own Composer Ai Editor groups. Ask a team administrator.

If the panel says Ask AI isn't set up for this environment, the environment has not been configured for Ask AI yet. That is a RuleCMS setup step.

How this fits

Ask AI does not replace the editor. Everything it builds is a rule you could have built by hand, with the same operators, and you can change it by hand afterwards. Dry run, Save, and publish work exactly as they do without it.