Mostly. Free Spectra stores most block attributes and CSS in the same _uagb_blocks_css postmeta and the uag_blocks_css table, so the bot can answer block visibility and styling questions without Pro. Loop Builder, Conditional Display, Popup Builder, Dynamic Content, and Custom Fonts answers all require Spectra Pro to be active.

Out of the box the Wizard exposes _uagb_blocks_css, _uagb_blocks_css_dependencies, _uagb_buttons_css, the uag_blocks_css table, and the Spectra Pro modules option. You can map any other postmeta key or option in two clicks if you have custom Spectra integrations like a third-party block.

Yes. File Generation writes block CSS to physical files under uploads/uag-plugin/. The bot can tell you whether File Generation is enabled, when the cache was last regenerated, and which file corresponds to the current post. That helps when a CSS change does not appear because the file is stale.

Yes. The bot reads the Loop Builder block attributes, including post type, taxonomy filters, posts per page, and ordering. It can explain why the loop returns zero items, which is almost always a mismatched taxonomy term or a date filter that excludes everything published in the period.

Custom Fonts uploads are recorded in option keys. The bot can list the active custom fonts, which weights are loaded, and which selectors use each font. That is useful when the design team adds a font that looks bigger than expected, because the bot can quote the actual font face and size in use.

Only to the LLM provider whose key you supply. SleekAI sends the context the system message requests to OpenAI, Anthropic, Google, or OpenRouter under your own account, and you pick the model. Nothing routes through SleekAI servers and you can pin everything to a strict retention provider.

Yes if you map the Popup Builder post type. The bot can quote each popup's trigger, delay, scroll threshold, exit intent rule, and which pages it appears on. That makes it easier to debug a popup that fires too often or not at all without opening five admin tabs in a row.

Yes. Display conditions support user role, logged-in state, and URL pattern. A typical setup limits the editor copilot to administrators and editors on /wp-admin/post.php and /wp-admin/post-new.php, while a separate public FAQ bot answers visitor questions under multibot on the live site.