Since WordPress 7 introduced the native Connectors API / AI Client, we've had questions from the community: "Why isn't Fabio Chatbot using it yet?" π€
Short answer: security concerns we're not ready to compromise on. π‘οΈ
Right now, API key handling in Fabio Chatbot is explicit β site owners set their own keys directly in the plugin's interface, and we control exactly how they're stored and used. Moving to the native connector means handing that responsibility to a layer we don't fully control yet, and we'd rather wait until it's proven stable and secure at scale than ship a migration that puts user credentials at risk. β οΈ We'll revisit this once WordPress core simplifies and hardens that connection flow.
In the meantime, we focused this release on something we could improve safely: response tone quality. π―
Fabio Chatbot has always offered three response tones β Professional, Friendly, and Serious β each driven by a dedicated system prompt that shapes vocabulary, structure, and energy. In 3.6.9.2, we refined the prompt logic behind all three:
- π¦ Professional: tighter enforcement of confident, sales-oriented language without drifting into generic AI-assistant phrasing
- π¨ Friendly: more consistent warmth without overusing emojis or exclamation marks π
- π₯ Serious: stricter adherence to clinical, fact-only output β no accidental persuasion creeping in
These tones aren't user-customizable β they're fixed presets you select from the admin panel βοΈ, tuned to be predictable and on-brand out of the box. β
π¬ Curious how the prompt logic is structured, or have thoughts on the connector migration timeline? Drop a comment β happy to go deeper into the implementation. π
Top comments (0)