AI Assistant for Magento 2

An API key from the AI provider you choose: Anthropic (the default) or OpenAI. You create the key in your own provider account, and the provider bills you directly for what the assistant uses. The module itself makes no charge per question. Image generation for CMS page drafts needs an OpenAI key in any case. The keys are entered once under Stores > Configuration > CommerceGears > AI > AI Providers & Costs, shared by all CommerceGears AI modules (the free CommerceGears AI Core module, installed with the assistant).

That depends on the model, how much the assistant has to look up and the provider's prices, so there is no fixed figure. Every request is recorded with its token counts and cost in AI Assistant > Cost Analytics, per user, model and conversation, at the prices in AI Providers & Costs > Costs > Model Prices (check them against your provider's pricing page). You can limit Questions per User per Day, set a Monthly Budget for all AI modules in AI Providers & Costs and, if you like, an AI Assistant Monthly Limit (USD) for the assistant alone. Saved reports under Ready Reports run in the store database and cost nothing.

Admin users whose role has AI Assistant > Chat. A store can narrow this further (for example to a list of named users); users kept away see nothing of the AI Assistant. CSV reports from the chat contain real customer data, so give the Chat permission only to roles that may see it.

It cannot change or delete existing data. Every query it writes runs on a separate connection in read-only transactions, so MySQL itself rejects INSERT, UPDATE, DELETE and similar statements. It can only create new things through four write tools defined in the module's code: issue tickets, scheduled questions, inactive CMS pages and inactive cart price rules. Each one needs its own role permission, shows a summary written by the server with Yes and No buttons, is created only after Yes and is recorded in the write log (bin/magento commercegears:ai-assistant:write-log).

The questions, the store data the assistant reads to answer them and, when it looks at code, parts of the store's source code. Names, e-mail addresses, phone numbers, addresses, credentials and similar values are masked before they leave the store, and password hashes and tokens are hidden even in CSV reports. Files such as env.php and auth.json cannot be read at all. Check that your provider's terms and your data protection duties allow this before you switch the module on.

Anthropic is the default and the module's reference provider. OpenAI works with the same tools, permissions, read-only connection, masking, confirmation and budget. Every answer shows which provider and model wrote it, and conversations continue when you switch.

No. CMS pages and cart price rules made by the assistant are always created inactive. A CMS draft can be checked through a signed preview link that only admins with the Pages permission get, valid for one hour. You activate the page or rule yourself in the usual Magento screens. Both draft tools can also be switched off in Capabilities.

Yes, once a report is saved. Ask the assistant for a report once; after the CSV it offers to save it under AI Assistant > Ready Reports. From then on you download it there with new dates (or other filters), with no model involved and at no cost.

The assistant answers in the language the user writes in. The admin screens come with English and Turkish translations; other languages can be added with a standard Magento translation file.

No. The module works in the admin only. Daily summaries, scheduled questions and test runs run in their own cron group (commercegears_ai_assistant), so they do not delay other cron jobs. The only storefront part is the admin-only preview of CMS drafts, which is never cached and marked noindex.

Yes. Choose CMS pages (for example returns, shipping or FAQ) under Capabilities > Knowledge Base Pages and the assistant reads them for process questions and links the source page. Describe your integrations, custom tables and status codes under Store Knowledge > Store Instructions. With Store Memory on, the assistant also offers to remember what it worked out about your store; after Yes the note appears under AI Assistant > Store Notes, where you can correct, turn off or delete it.

With New Relic set up (a User API key of a read-only user), the assistant can query errors and slow transactions. Other systems are not queried directly: the assistant uses the statuses your integrations save in the store database.

Yes. After a CSV report the assistant offers to save it under Ready Reports with filters such as a date range. You then download it there with new values, without the assistant and at no cost.