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

[Feature]: Embed a Quivr chat on a website #1791

Closed
StanGirard opened this issue Dec 2, 2023 · 4 comments
Closed

[Feature]: Embed a Quivr chat on a website #1791

StanGirard opened this issue Dec 2, 2023 · 4 comments
Labels
adventofcode area: backend Related to backend functionality or under the /backend directory area: frontend Related to frontend functionality or under the /frontend directory enhancement New feature or request good first issue Good for newcomers Stale

Comments

@StanGirard
Copy link
Collaborator

The Feature

image

I'd like users to be able to embed a chat on their website. The chat would be connected to a brain. Allowing people to create chatbots on their websites easily.

Motivation, pitch

Would be amazing

Twitter / LinkedIn details

No response

@StanGirard StanGirard added the enhancement New feature or request label Dec 2, 2023
Copy link

dosubot bot commented Dec 2, 2023

🤖

Hi @StanGirard! Good to see you back here in the Quivr repository. I hope you're doing well.

Thank you for your feature request. Embedding a Quivr chat on a website could indeed be a powerful feature, allowing users to create chatbots easily.

Based on the current architecture of Quivr, it does have an API that can be used to facilitate communication between a website and the Quivr brain. This is a good starting point for implementing the chat feature you're suggesting. However, it's important to note that real-time communication, which is essential for chat functionality, is not explicitly mentioned in the repository. This might be a challenge that needs to be addressed.

Here's a basic example of how the API could be used to interact with the Quivr brain:

# Set up the request payload
payload = {
    "name": random_brain_name,
    "status": "public",
    "model": "gpt-3.5-turbo",
    "temperature": 0,
    "max_tokens": 256,
    "brain_type": "doc",
}

# Making a POST request to the /brains/ endpoint
response = client.post(
    "/brains/",
    json=payload,
    headers={"Authorization": "Bearer " + api_key},
)

This code creates a new brain by making a POST request to the "/brains/" endpoint. A similar approach could be used to send and receive messages from the Quivr brain, which would be the basis for the chat functionality.

However, implementing this feature would likely require significant changes to the Quivr codebase and architecture. It would also require careful consideration of security and privacy issues, as the chat would be connected to a brain and potentially handling sensitive information.

I hope this gives you a better understanding of the potential challenges and considerations for this feature. If you have any further questions or need more information, please let me know.

Sources


This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

@dosubot dosubot bot added area: backend Related to backend functionality or under the /backend directory area: frontend Related to frontend functionality or under the /frontend directory labels Dec 2, 2023
@MeTaNoV
Copy link
Contributor

MeTaNoV commented Dec 6, 2023

@StanGirard we can discuss this in details since I did an integration of some UI component already but it is not that straightforward...

@StanGirard
Copy link
Collaborator Author

@MeTaNoV what i started to do is implement a way to create api keys that can only chat with brains and nothing else.

And yes that would be awesome to reuse components.

Copy link
Contributor

github-actions bot commented Jan 5, 2024

Thanks for your contributions, we'll be closing this issue as it has gone stale. Feel free to reopen if you'd like to continue the discussion.

@github-actions github-actions bot added the Stale label Jan 5, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
adventofcode area: backend Related to backend functionality or under the /backend directory area: frontend Related to frontend functionality or under the /frontend directory enhancement New feature or request good first issue Good for newcomers Stale
Projects
None yet
Development

No branches or pull requests

2 participants