Skip to content
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

Add RecurseChat #1548

Merged
merged 1 commit into from
Nov 1, 2024
Merged

Add RecurseChat #1548

merged 1 commit into from
Nov 1, 2024

Conversation

xyc
Copy link
Contributor

@xyc xyc commented Oct 31, 2024

Types of Changes

What types of changes does your PR introduce? Put an x in all boxes that apply

  • New addition to list
  • Fixing bug in existing item in list
  • Removing item from list
  • Changing structure (organization) of list

Proposed Changes

Adding RecurseChat to the list since it offers unique value to users seeking a privacy-focused AI chat experience 😊. It's a local-first chat application with AI that prioritizes user privacy while providing powerful customization options. Some standout features:

  • Personal and private: Runs locally on your machine, keeping your conversations secure
  • Simple yet powerful interface: Clean design with extensive customization options
  • Fast performance: Optimized for quick responses and smooth interaction
  • Local-first architecture: Works offline and keeps your data under your control

The app fills an important niche for users who want the benefits of AI chat while maintaining control over their data and privacy.

PR Checklist

Put an x in the boxes once you've completed each step. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • I have read the CONTRIBUTING guide
  • I have explained why this PR is important
  • I have added necessary documentation (if appropriate)

Further Comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

@jaywcjlove jaywcjlove merged commit 80184ea into jaywcjlove:master Nov 1, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants