No. Better Search Replace runs the actual UPDATE queries through its admin UI. SleekAI is a separate plugin that helps the admin reason about what to select and what to expect. The chatbot does not have permission to execute SQL or trigger the replacement, which is by design so that destructive operations stay behind the explicit dry-run plus confirm flow that Better Search Replace already provides.

Only when there is a real risk. Better Search Replace itself is serialization-aware and walks PHP serialized arrays correctly. The bot's system prompt encodes that behavior, so it will not raise false alarms about wp_options blobs. It will, however, warn about non-PHP-serialized formats like JSON inside text columns that the plugin does not adjust automatically, useful when sites store data in less common shapes.

Yes. The Wizard maps the current site's table list, drawn from the database's information_schema, so the bot's answers reflect your actual schema. That matters on sites with custom plugin tables, custom prefixes, or multisite installs where the bot needs to know that wp_2_options exists alongside wp_options and which one applies to the current operation.

No. Display conditions are typically set to administrator role only and to the Tools screen URL pattern. Editors, authors, and subscribers do not see the bot at all. That keeps the assistant invisible to anyone who would not be running a search-and-replace anyway and prevents prompt-engineered attempts to coax it into revealing schema details from visitor traffic.

Better Search Replace stores recent progress and result data under wp_options, so the bot can read the most recent dry-run report and reference its row counts per table. That is useful for the typical workflow where an admin runs a dry-run, asks the bot to interpret the counts, then decides whether the production run is safe to execute based on what the report showed.

Yours. SleekAI is bring-your-own-key, so message costs are billed directly by your provider with no SleekWP markup. Use OpenAI, Anthropic, Google, or OpenRouter, and pick a fast model for quick table-list lookups and a stronger one for reasoning about complex multi-step migrations under the same chatbot without changing the integration.

No. The chat widget is lazy and only initializes when an admin opens it. SleekAI reads table lists and recent BSR option data on the chat request, not on every page load of the admin. Most chat sessions involve a few queries against bounded options rows and the WordPress database schema, well within the budget of a normal admin interaction.

Yes. On multisite, the Wizard can map each site's table prefix separately, so wp_2_options and wp_3_options resolve correctly when the admin is operating on a specific subsite. The bot scopes its answers to the current subsite's prefix to avoid the common foot-gun of accidentally pasting a replacement target table from a different blog ID into the search-and-replace UI.