Skip to content

FEATURE: Configure persona backed features in admin panel #1245

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 12 commits into from
Apr 10, 2025

Conversation

keegangeorge
Copy link
Member

@keegangeorge keegangeorge commented Apr 2, 2025

🔍 Overview

In this feature update, we add the UI for the ability to easily configure persona backed AI-features. The feature will still be hidden until structured responses are complete.

📸 Screenshots

Screenshot 2025-04-09 at 09 24 41
Screenshot 2025-04-09 at 09 24 55

Comment on lines -108 to -111
include_condition: -> do
SiteSetting.ai_bot_enabled && scope.authenticated? &&
scope.user.in_any_groups?(SiteSetting.ai_bot_allowed_groups_map)
end,
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am removing the dependency for SiteSetting.ai_bot_enabled to add ai_enabled_personas to current user serializer. Since we want features to be backed by personas, I don't think it should be dependant on AI bot anymore.

Also, discobot discoveries uses ai_bot_enabled for it's enabling setting, so if we disable discoveries in the feature list, then the dropdown to show personas will no longer work.

@keegangeorge keegangeorge requested a review from Copilot April 4, 2025 22:25
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 16 out of 20 changed files in this pull request and generated 1 comment.

Files not reviewed (4)
  • admin/assets/javascripts/discourse/templates/admin-plugins/show/discourse-ai-features/edit.gjs: Language not supported
  • admin/assets/javascripts/discourse/templates/admin-plugins/show/discourse-ai-features/index.gjs: Language not supported
  • assets/javascripts/discourse/components/ai-feature-editor.gjs: Language not supported
  • assets/stylesheets/common/ai-features.scss: Language not supported

@keegangeorge keegangeorge marked this pull request as ready for review April 7, 2025 16:41
@keegangeorge keegangeorge requested a review from xfalcox April 7, 2025 19:26
…ture (#1248)

This update makes use of the `area` key in `settings.yml` to show all settings related to particular features inside their feature tab editor. This allows admins to easily configure features and parse through a variety of different settings.
@xfalcox xfalcox requested a review from Copilot April 9, 2025 20:07
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 21 out of 24 changed files in this pull request and generated no comments.

Files not reviewed (3)
  • admin/assets/javascripts/discourse/templates/admin-plugins/show/discourse-ai-features/edit.gjs: Language not supported
  • admin/assets/javascripts/discourse/templates/admin-plugins/show/discourse-ai-features/index.gjs: Language not supported
  • assets/stylesheets/common/ai-features.scss: Language not supported
Comments suppressed due to low confidence (1)

lib/ai_bot/entry_point.rb:108

  • The updated inclusion condition for the current user serializer removes the checks for 'ai_bot_enabled' and group membership, which might alter the intended access control behavior. Please confirm that this change is intentional.
          include_condition: -> { scope.authenticated? },

@keegangeorge keegangeorge merged commit 4de39a0 into main Apr 10, 2025
6 checks passed
@keegangeorge keegangeorge deleted the admin-config-features branch April 10, 2025 15:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants