For full release notes of each version, see GitHub Releases.
2.4.0
Add an AI Model setting to pin the provider/model used for AI Overview. Only configured connectors (WordPress 7.0 Settings → Connectors) are listed, and if the chosen model later becomes unavailable it falls back to auto-selection instead of failing.
Change the default temperature to omitted. Some models (e.g. Claude Opus/Sonnet) reject a temperature and returned a 400 error when auto-selected; omitting is safe for every model. Set a value on the settings page only if you need it.
Add hamelp_ai_model and hamelp_ai_temperature filters to override the model and temperature from code.
Improve source citations: rename the “Related FAQs” heading to Sources, and render the list as a numbered (ordered) list so its numbers line up with the inline (Ref. N) citations in the answer.
2.3.1
User can change the reference prefix (Ref. 1).
2.3.0
Change ownership to Tarosky.
Rename the plugin to PubPla AI Help Center. The plugin slug, text domain, REST routes, and PHP APIs stay hamelp for backward compatibility, so no configuration or code changes are required.
AI Overview now supports multi-turn conversations. Follow-up questions keep the previous exchanges as context, and answers stack as a Q&A thread. Conversation history is held in the browser and sent with each request, so nothing is stored on the server.
Add hamelp_history_window filter to limit how many prior messages are sent to the LLM (default 10).
Optionally save conversations for question mining (off by default). When enabled on the settings page, conversations are stored as a private post type viewable in the admin, so you can see what visitors actually ask. Toggle via the Save Conversations setting or the hamelp_save_conversations filter.
Add an Auto-delete After (days) retention setting. A daily cron removes anonymous conversations older than the configured number of days (0 = never delete). Conversations from logged-in users are never auto-deleted.
Add an AI Overview Mode setting: Conversation (multi-turn, default), Single answer (no follow-up, lower cost), or Disabled. Use Single/Disabled to cut cost or stop the feature during a request flood. Also available via the hamelp_ai_overview_mode filter.
The front-end now reflects the mode: Single answer replaces the previous answer on each question, and Conversation shows a “Continue the previous conversation” toggle so visitors can either keep asking follow-ups or start a fresh conversation (which clears the thread).
2.2.3
Change CSS structure –wp–preset–color–* to fit with Theme design. Thank you bissy for Pull requests.
2.2.2
Add FAQ Search Box block (hamelp/search-box). The existing [hamelp-search] shortcode continues to work and now shares the same render logic.
Expose hamelp_render_search_box() as a public template function so themes can render the search box without going through the shortcode parser.
2.2.0
Remove bundled wp-ai-client Composer dependency. AI Overview now uses the wp-ai-client bundled with WordPress core, which requires WordPress 7.0 or later.
On WordPress versions earlier than 7.0, the AI Overview block and search form still render but submissions fail (no REST route). FAQ custom post type, incremental search, and other features remain functional.
Auto-rebuild the FAQ catalog on plugin activation, so the AI Overview works out of the box without manually running wp hamelp rebuild.
Add a Rebuild Catalog Now button to the settings page for manual catalog refresh.
2.1.0
Add user context to AI Overview for personalized responses.
Add whitelist-based user role filtering for security (hamelp_allowed_user_roles filter).
Add hamelp_user_context and hamelp_display_user_roles filters for customization.
Add development hooks support for local environment testing.
Remove bundled translations in favor of GlotPress (WordPress.org).
