Feat Pro Users Whitelist

[AndlerRL]

Summary by Sourcery

Implement a whitelist feature for pro users, restricting access to pro models based on a predefined list of email addresses

New Features:

• Added whitelist functionality for pro user model access

Enhancements:

• Modified user access logic to check against a whitelist of pro user emails

Chores:

• Updated configuration to support pro user whitelist
• Adjusted page sizes in constants

Summary by CodeRabbit

• New Features
  • Introduced user email whitelisting for access to pro models.
• Improvements
  • Enhanced prompt instructions to include both questions and statements.
  • Adjusted display logic for thread panels to better separate visual elements and no-results messaging.
• Bug Fixes
  • None.
• Configuration
  • Added a new configuration option for specifying pro model access whitelist via environment variables.
• Performance & Usability
  • Reduced default pagination sizes for improved loading performance.
• Data Retrieval
  • User email is now included when fetching user details.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
masterbots	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 3, 2025 0:10am

[coderabbitai]

Walkthrough

This update introduces a user email whitelist for gating access to pro models in the chat combobox, using a new configuration property populated from an environment variable. The logic for displaying certain UI elements in the user thread panel is refined, separating the rendering of a horizontal rule and a no-results message. Page size constants are reduced, and the prompt for improving user questions now explicitly includes statements. The user retrieval service now fetches the user's email, and the environment configuration is extended to support the new whitelist feature.

Changes

File(s)	Change Summary
apps/masterbots.ai/components/routes/chat/chat-combobox.tsx	Added a whitelist check for user emails to control pro model access, using a new config property.
apps/masterbots.ai/components/routes/thread/user-thread-panel.tsx	Separated the rendering logic for <hr> and NoResults components for clearer UI behavior.
apps/masterbots.ai/lib/constants/hasura.ts	Reduced PAGE_SIZE from 20 to 10 and PAGE_SM_SIZE from 10 to 5.
apps/masterbots.ai/lib/constants/prompts.ts	Updated prompt text to include "(and/or statements)" alongside "questions" for broader applicability.
apps/masterbots.ai/services/hasura/hasura.service.ts	Modified user query to also retrieve the email field.
packages/mb-env/src/config.env.ts	Added proWhitelistUsers property to the config, parsing it from an environment variable.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant ChatCombobox
    participant Config
    participant HasuraService

    User->>ChatCombobox: Attempt to access pro model
    ChatCombobox->>Config: Retrieve proWhitelistUsers
    ChatCombobox->>HasuraService: Get current user (including email)
    HasuraService-->>ChatCombobox: Return user data with email
    ChatCombobox->>ChatCombobox: Check if user email in whitelist
    alt Email in whitelist and pro subscription
        ChatCombobox-->>User: Grant pro model access
    else Not in whitelist or no subscription
        ChatCombobox-->>User: Deny pro model access
    end

Loading

Possibly related PRs

• bitcashorg/masterbots#445: Also modifies feature gating logic in chat-combobox.tsx, focusing on model list display flags.
• bitcashorg/masterbots#476: Alters gating logic in chat-combobox.tsx by removing a dev mode guard, related to model selection access.

Suggested labels

feature, backend

Suggested reviewers

• Bran18

Poem

A whitelist now opens the pro model gate,
With emails checked, access is up-to-date.
Prompts now welcome statements too,
Page sizes shrink for a tighter view.
The user’s email fetched with care,
Configuration magic fills the air.
🐇✨ Code hops forward, fair and square!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Lite

📥 Commits

Reviewing files that changed from the base of the PR and between 04b643c and 79188b9.

📒 Files selected for processing (1)

• packages/mb-env/src/config.env.ts (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• packages/mb-env/src/config.env.ts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sourcery-ai]

Reviewer's Guide

This pull request introduces a whitelist feature for Pro users, restricting access to Pro models based on both subscription status and inclusion in a new email whitelist defined via an environment variable. It also adjusts pagination constants, updates prompt wording, and refactors UI logic in the user thread panel.

Sequence diagram for Pro model access check

sequenceDiagram
    actor User
    participant ChatCombobox
    participant UserDataService
    participant AppConfig

    User->>ChatCombobox: Interact with model selector
    ChatCombobox->>UserDataService: Get user data (incl. email, pro status)
    UserDataService-->>ChatCombobox: Return user data
    ChatCombobox->>AppConfig: Get Pro Whitelist
    AppConfig-->>ChatCombobox: Return proWhitelistUsers list
    ChatCombobox->>ChatCombobox: Check if user has Pro sub AND is in whitelist
    alt User is Pro AND Whitelisted
        ChatCombobox-->>User: Enable Pro models
    else User is not Pro OR not Whitelisted
        ChatCombobox-->>User: Disable Pro models
    end

Loading

Class diagram for Configuration and User Data Changes

classDiagram
    class AppConfig {
        +features: Features
    }
    class Features {
        +devMode: boolean
        +enableVerificationEmail: boolean
        +profileNBotPageHasPopup: boolean
        +proWhitelistUsers: string[]
    }
    class User {
        +userId: string
        +username: string
        +profilePicture: string
        +email: string
        +slug: string
        +bio: string
        +favouriteTopic: string
        +proUserSubscriptionId: string
        # ... other fields
    }
    class ChatCombobox {
        # ... existing properties/methods
    }
    note for ChatCombobox "Logic updated to disable Pro models if user is not Pro OR not in proWhitelistUsers"

Loading

File-Level Changes

Change	Details	Files
Implement Pro User Whitelist functionality.	Added a proWhitelistUsers feature flag derived from the NEXT_PUBLIC_PRO_WHITELIST_USERS environment variable. Updated the chat combobox component to disable Pro models unless the user is subscribed AND their email is in the whitelist. Modified the getUserBySlug service to fetch the user's email.	packages/mb-env/src/config.env.ts apps/masterbots.ai/components/routes/chat/chat-combobox.tsx apps/masterbots.ai/services/hasura/hasura.service.ts
Adjust pagination size constants.	Reduced PAGE_SIZE from 20 to 10. Reduced PAGE_SM_SIZE from 10 to 5.	apps/masterbots.ai/lib/constants/hasura.ts
Update prompt wording.	Replaced occurrences of "question" with "question (and/or statement)" for broader applicability.	apps/masterbots.ai/lib/constants/prompts.ts
Refactor UI rendering logic in User Thread Panel.	Separated the rendering conditions for the horizontal rule and the 'No Results' component.	apps/masterbots.ai/components/routes/thread/user-thread-panel.tsx

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[Copilot]

Pull Request Overview

This PR implements the Pro Users Whitelist feature by adding a new configuration for pro whitelist users and incorporating whitelist checks in the chat component while adjusting related settings and UI behavior.

• Introduces proWhitelistUsers in the environment configuration.
• Updates the Hasura service to include the email field.
• Adjusts wording in prompts, pagination sizes, and thread panel render conditions.
• Adds an additional whitelist check in the chat-combobox component.

Reviewed Changes

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

Show a summary per file

File	Description
packages/mb-env/src/config.env.ts	Adds proWhitelistUsers configuration by splitting the NEXT_PUBLIC_PRO_WHITELIST_USERS environment variable.
apps/masterbots.ai/services/hasura/hasura.service.ts	Includes the email field in the getUserBySlug query.
apps/masterbots.ai/lib/constants/prompts.ts	Updates prompt text for clarity.
apps/masterbots.ai/lib/constants/hasura.ts	Modifies pagination constants.
apps/masterbots.ai/components/routes/thread/user-thread-panel.tsx	Adjusts conditional rendering to consider the loading state.
apps/masterbots.ai/components/routes/chat/chat-combobox.tsx	Adds a whitelist check for the users’ email on pro model access.

Comments suppressed due to low confidence (1)

packages/mb-env/src/config.env.ts:26

• Consider filtering out empty strings from the resulting array to avoid unintended behavior when the environment variable is not set, as splitting an empty string results in [''].

proWhitelistUsers: (process.env.NEXT_PUBLIC_PRO_WHITELIST_USERS || '').split(',')

[sourcery-ai]

Hey @AndlerRL - I've reviewed your changes - here's some feedback:

• This pull request combines the pro user whitelist feature with unrelated changes (prompts, UI, pagination).
• Consider if exposing the entire pro user whitelist via a public environment variable is the desired approach.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (2)

packages/mb-env/src/config.env.ts (1)

26-28: Trim whitespace from email addresses in whitelist.

Email addresses with leading or trailing spaces could cause issues when comparing with user emails.

Consider trimming whitespace:

-proWhitelistUsers: (
-	process.env.NEXT_PUBLIC_PRO_WHITELIST_USERS || ''
-).split(','),
+proWhitelistUsers: (
+	process.env.NEXT_PUBLIC_PRO_WHITELIST_USERS || ''
+).split(',').filter(Boolean).map(email => email.trim()),

apps/masterbots.ai/components/routes/chat/chat-combobox.tsx (1)

108-112: Consider handling edge cases with the whitelist implementation.

The whitelist implementation works as expected, but there are some edge cases to consider:

1. If NEXT_PUBLIC_PRO_WHITELIST_USERS is empty, WHITELIST_USERS will be [''], which could disable pro models for all users.
2. The email comparison is case-sensitive, which might cause issues if emails are stored with different casing.

Consider updating the condition to handle these edge cases:

const areProModelsDisabled =
  !appConfig.features.devMode &&
  (loadingUserData ||
    !userData?.proUserSubscriptionId ||
-   !WHITELIST_USERS.includes(userData?.email))
+   !(WHITELIST_USERS.length === 1 && WHITELIST_USERS[0] === '' ? 
+     true : // Allow all pro users if whitelist is empty
+     WHITELIST_USERS.includes(userData?.email?.toLowerCase())))

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d11a1a1 and 04b643c.

📒 Files selected for processing (6)

• apps/masterbots.ai/components/routes/chat/chat-combobox.tsx (2 hunks)
• apps/masterbots.ai/components/routes/thread/user-thread-panel.tsx (1 hunks)
• apps/masterbots.ai/lib/constants/hasura.ts (1 hunks)
• apps/masterbots.ai/lib/constants/prompts.ts (1 hunks)
• apps/masterbots.ai/services/hasura/hasura.service.ts (1 hunks)
• packages/mb-env/src/config.env.ts (1 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (2)

apps/masterbots.ai/lib/constants/prompts.ts (1)

apps/masterbots.ai/lib/threads.ts (1)

• getAllUserMessagesAsStringArray (21-37)

apps/masterbots.ai/components/routes/chat/chat-combobox.tsx (1)

packages/mb-env/src/config.env.ts (1)

• appConfig (2-41)

🔇 Additional comments (7)

apps/masterbots.ai/lib/constants/hasura.ts (1)

1-2: Reducing page sizes could impact UX.

Reducing PAGE_SIZE from 20 to 10 and PAGE_SM_SIZE from 10 to 5 will reduce the number of items loaded per request, which may improve initial load performance but could lead to more pagination interactions.

Ensure that the UI properly handles these smaller page sizes and that pagination controls are clearly visible to users.

apps/masterbots.ai/services/hasura/hasura.service.ts (1)

1281-1281: Email field added for pro whitelist feature.

Adding the email field is necessary for the pro users whitelist implementation. This change is essential for checking if a user's email is in the whitelist defined in the environment configuration.

apps/masterbots.ai/lib/constants/prompts.ts (2)

19-19: Include statements alongside questions for improved flexibility.

Expanding the prompt to handle both questions and statements makes the system more versatile and user-friendly.

---

24-25: Updated guidelines to accommodate both questions and statements.

These changes ensure the language used in the prompt is inclusive of both question and statement inputs, which aligns with the broader goal of improving the handling of user input.

apps/masterbots.ai/components/routes/chat/chat-combobox.tsx (1)

32-33: New whitelist feature for controlling access to pro models.

The constant WHITELIST_USERS references the new whitelist configuration from appConfig.features.proWhitelistUsers, which will be used to gate access to pro models based on user emails.

apps/masterbots.ai/components/routes/thread/user-thread-panel.tsx (2)

439-441: Improved horizontal rule rendering condition.

The horizontal rule now has a more specific rendering condition, only appearing when all threads are loaded (totalThreads === count), threads exist, and loading is complete. This prevents the separator from appearing during loading states or when no results are shown.

---

442-448: Better separation of no-results message rendering.

The NoResults component now renders independently from the horizontal rule, only when showNoResults is true. This improves the clarity of the UI logic by separating these two distinct visual elements.

[AndlerRL]

Andler Development Support - May 2025