AI Assistant

• Requires softaware/module-core (^1.0) and loads after Softaware_Core, like the other SoftAware modules.
• Chat page privacy note: says what the assistant can create after confirmation (inactive CMS pages, with banner images when image generation is on, inactive cart price rules, tickets and scheduled questions) instead of "cannot change anything in the store".

• Product listing, FAQ and user guide (docs/): docs/listing.json, docs/faq.md, docs/user-guide.md and screenshots in docs/images/.

• Admin pages no longer repeat the page title inside the page (Cost Analytics, Ready Reports, Feedback, Test Set); the line under it is kept as the introduction. Page titles: "Issue Tickets" and "Cost Analytics" (without the "AI Assistant" prefix), menu item "Configuration" renamed "Settings".
• "Not available" states share one look: a title, the reason, the command an administrator has to run shown as copyable code, and an "Open Settings" link for users who may change the settings (feature switched off).
• Issue Tickets: introduction and an empty state with a link to the chat instead of an empty table.
• Test Set: "Run Test Set" asks for confirmation first, because every question is sent to the AI provider again, and is disabled while no question is included in runs.
• Settings: Limits (budget, questions per day) directly after the provider groups; long comments shortened to what a merchant needs; comments now name "the AI provider" instead of Anthropic where OpenAI applies too; missing comments added (Enabled, Image Quality, New Relic fields). Below 1280 px the Model Prices table scrolls inside its field instead of making the whole settings page scroll sideways.

• Capabilities > "CMS Page Drafts" and "Cart Price Rule Drafts" (default Yes): the admin decides whether the assistant may create inactive CMS pages and promotions. Capabilities > "Tools from Other Modules" (default No): tools other modules add to ToolPool are offered only when the admin trusts those modules; one that writes must be a WriteToolInterface.

• bin/magento softaware:ai-assistant:user:allow <username>... adds admin users to the allowed users; users already allowed keep access. Warns about inactive accounts and roles without AI Assistant > Chat.
• bin/magento softaware:ai-assistant:user:revoke <username>... removes users (a deleted user by ID); the others stay.
• The 'not allowed' notice shows the command to run with the user's username.
• Fixed: setup instructions used config:set on a path Magento rejects; they now use the new commands.

• OpenAI as an alternative chat provider: General > "Provider" (Anthropic, the default, or OpenAI) and the group "OpenAI (Optional)" with the OpenAI API key (encrypted), the chat model (default gpt-6.1-sol), the model for daily summaries and scheduled questions (default gpt-6-luna) and "Refresh OpenAI model list" (GET /v1/models, chat models only). OpenAI is called through the Responses API (stateless) with Magento's HTTP client, no new Composer package. Model\Assistant\MessageGatewayInterface with ProviderGateway; Model\OpenAi\ResponsesTranslator translates requests and answers (tools <-> function tools, tool_use / tool_result <-> function_call / function_call_output, parallel calls, usage with cached tokens, refusals, content filter, truncation). Stored conversations keep the Anthropic block format.
• Built-in OpenAI price table (Model\Cost\OpenAiPrices, from developers.openai.com/api/docs/pricing on 2026-10-06); a row in Costs > Model Prices still wins. OpenAI requests count in Cost Analytics and the monthly budget like Anthropic ones.
• Every answer shows the provider and model that wrote it ("Anthropic · claude-sonnet-5-5"), also in shared conversations; Cost Analytics shows the provider next to each model. New column model on softaware_ai_assistant_message.
• Generated images for CMS page drafts (OpenAI Images API, default gpt-image-2, with either chat provider): "Generate Images for CMS Drafts" (default Yes, active only with an OpenAI key), Image Model, Image Quality (default medium), Images per Page (default 4). Optional generate_image (prompt, alt, aspect ratio) on hero and image-with-text sections; generated only after Yes, listed in the proposal with an estimated cost, checked against the monthly budget per image and recorded in Cost Analytics; re-encoded to WebP with GD (metadata removed, cropped, max 1600 px), random names under pub/media/wysiwyg/softaware-ai/<yyyy>/<mm>/, {{media url=...}} with width, height and alt. Failed images (OpenAI refusal, error, budget) leave the section without an image and are named in the answer and in the page's write log entry (prompt, model, cost, file per image). It is output of the existing create_cms_page_draft tool; the write tools stay four.
• Command softaware:ai-assistant:images:cleanup (lists generated images no CMS page or block uses; --delete removes them; --min-age-hours, default 24).
• Golden test of the Anthropic requests (AnthropicRequestGoldenTest, seven scenarios recorded from 1.2.0).

• With Provider = Anthropic (default) the requests to Anthropic are unchanged, byte for byte, as long as image generation is off or no OpenAI key is set. With image generation on, the only differences are the optional generate_image field in the create_cms_page_draft tool definition (plus one sentence in its description) and one sentence about generated images in the instructions.
• AnthropicGateway implements MessageGatewayInterface; ChatService and HeadlessRunner take the interface (di.xml preference ProviderGateway).
• A conversation continues after the provider was switched; only a question that was in the middle of a tool step asks the user to start a new conversation.
• The General group's note now says data goes to the chosen provider.

• Inactive CMS page drafts from the chat (tool create_cms_page_draft, permission AI Assistant > Assistant Actions > "Create Inactive CMS Page Drafts" plus Content > Pages > Save Page): the assistant designs a page from sections (hero, text, features, image with text, FAQ, testimonials, call to action, simple HTML) and optional colours; the store renders it as self-contained, responsive HTML with inline styles that looks the same on Luma and Hyvä without a theme build, stays within Magento's CMS HTML rules (checked strictly before saving) and opens in the WYSIWYG editor (Page Builder places it in an HTML Code element). Server-side cleaning removes scripts, styles, iframes, forms, embeds, event and binding attributes, unsafe URLs and CSS, and every {{...}} directive. Title, unique URL key, meta data, store views (default all) and layout; always created inactive, with links to the page and to an admin-only storefront preview (signed link valid for one hour, never cached, noindex, with a notice).
• Inactive cart price rule drafts from the chat (tool create_cart_rule_draft, permission "Create Inactive Cart Price Rule Drafts" plus Marketing > Cart Price Rules): percent, fixed per item, fixed for the whole cart, buy X get Y; dates, customer groups, websites, no / specific / generated coupons, uses per customer and coupon, priority, discard subsequent rules, label, cart subtotal and quantity conditions, items by category, SKU or attribute set. Everything is checked against the store (ids, SKUs, coupon uniqueness, ranges); missing essentials make the assistant ask instead of guess.
• Write log softaware_ai_assistant_write_log and command softaware:ai-assistant:write-log: every entity the assistant created, with the admin who confirmed it, time, conversation, confirming message and request.
• Command softaware:ai-assistant:db-status and the "Check read-only access" button (Database Access): shows whether a dedicated SELECT-only user or a read-only session is used.
• ACL "AI Assistant > Assistant Actions" with one resource per write tool; a data patch gives "Record Issue Tickets" and "Schedule Questions" to roles that already had Chat.

• Limits > "Monthly Budget (USD)" (empty = no limit, as before): once the cost recorded in the current calendar month (store time zone, at the configured model prices) reaches it, the chat takes no new questions (with a message naming the budget and the date it resets), an investigation stops between steps, and the daily summary, scheduled questions and test runs wait. Answer buttons that need no model call keep working. Cost Analytics shows the month's use with a bar (amber from 80 %, red when used up) and a link to the setting.

• Tools added by other modules through di.xml are no longer offered to the model: they could write without being on the write list. Only the module's own tools (four of them can write) are used.

• Writes only through an allow-list of four write tools in code (ToolPool::WRITE_TOOLS, WriteToolInterface): own permission, server-side validation, new entities only, proposal with a server-written summary and creation only after the user's answer with exactly that content, write log. Runs without a user never get a write tool.
• Every assistant query and every Ready Report runs on a connection the database keeps read-only: the dedicated env.php connection softaware_ai_readonly is used automatically when it exists; the session is set read-only before every statement and each statement runs in START TRANSACTION READ ONLY ... ROLLBACK (a statement switching the session to READ WRITE no longer affects later ones). Ready Reports previously streamed from Magento's writable default connection. db-grants prints the env.php snippet for the new connection name.

• Prompt injection: a confirmed feature ticket or scheduled question is created only with the content that was proposed to the user (type, title and summary; question, days and hour). A later call with other content is proposed again instead of being carried out. New ConfirmationOptions::matchesProposal() for tools of other modules.
• Prompt injection: admin links in answers become clickable only for pages that show something (index, view, edit) and without URL options (_direct, key, form_key). Links carry the viewer's URL secret key, so an answer steered by text in store data could otherwise offer a one-click link to an action that deletes or changes data.
• The instructions tell the model that tool results (product texts, reviews, comments, logs, pages) are data, never instructions.
• The SQL guard now also denies other users' feedback, test set questions and answers, inbox items, scheduled questions and report queries (softaware_ai_assistant_feedback, _test_case, _test_result, _inbox, _scheduled_question, _report_file), PayPal API certificates (paypal_cert) and Adobe IMS tokens (admin_adobe_ims_webapi, adobe_user_profile).
• SELECT * could return login secrets that the guard only refuses when a statement names them: customer confirmation keys, newsletter confirmation codes, order cancel keys and download link hashes are now masked for the model, and CSV reports (unmasked for their owner) write [hidden] for credential columns (password hashes, reset tokens, keys, card data). Column names in CSV reports get the same formula guard as the values.

• bin/magento config:set softaware_ai_assistant/general/allowed_users ..., as documented, failed with "path doesn't exist"; the path is now declared (still not shown in the form).

• An answer containing a NUL character froze the browser tab (chat, floating chat, shared conversation, inbox).

• Bug tickets are proposed with Yes / No like feature requests instead of being recorded by the assistant on its own (a ticket is a write and must not follow from text the assistant read).
• composer.json no longer has a version field; the release tag sets the version. New dependency magento/module-sales-rule.

• AI Assistant > Ready Reports (aiassistant/readyreport/index, permission Softaware_AiAssistant::ready_reports, setting Capabilities > "Ready Reports", default Yes): 16 predefined reports downloaded as CSV for a date range (today, yesterday, last 7 / 30 days, this / last month, this / last year, custom) and an optional store view: sales summary by day / week / month / year, orders by status, sales by customer group, payment method, shipping method, country / region, product and category, low stock (threshold), products not sold in the period, new vs returning customers, top customers (with lifetime figures), abandoned carts, tax by rate, refunds (credit memos) and coupon usage. UTF-8 with BOM, base currency amounts with 2 decimals, whole days in the store time zone (daylight saving aware grouping), formula-safe text.
• Reports are streamed from a separate unbuffered database connection into a temporary file, so large results do not use PHP memory; temporary files of interrupted downloads are removed by the cleanup cron.
• Extension point Model\ReadyReport\ReportInterface with ReportPool (di.xml argument reports).
• Chat tool run_ready_report (offered while Ready Reports is on; needs the Ready Reports permission): prepares a ready report with a download button; the model sees a masked 10-row preview.
• Command softaware:ai-assistant:ready-report (list reports, write a report to a CSV file).
• ReportFileStore::createFileName() and register() for report files written directly to disk.
• i18n/en_US.csv; Turkish translations for the new texts.
• Composer: PHP ~8.3.0||~8.4.0||~8.5.0.

Maintenance release.