docs(gpt4): Update GPT-4 Documentation (#2573)

Updates the `docs/brains/gpt4.mdx` documentation to include detailed
instructions on adding a GPT-4 Brain to Quivr and configuring it within
the Supabase integration table.
- Adds a new section titled "Adding GPT-4 Brain to Quivr" that outlines
the steps required to integrate a GPT-4 Brain into Quivr, including
accessing the Supabase dashboard and navigating to the integration
table.
- Provides step-by-step instructions for adding a custom brain named
gpt4 in the Supabase integration table and configuring the necessary
settings for the GPT-4 Brain, such as API keys and preferences.


---

For more details, open the [Copilot Workspace
session](https://copilot-workspace.githubnext.com/QuivrHQ/quivr?shareId=81c5fd43-eb46-407c-a40f-c0b0b3a41925).
This commit is contained in:
Stan Girard 2024-05-10 10:49:45 +02:00 committed by GitHub
parent 3b494c807f
commit fb46bb9341
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -22,5 +22,25 @@ This is a brain that allows you to interact with GPT-4. You can ask questions to
</Step>
</Steps>
You now have a brain that can answer questions using GPT-4. You can ask your brain questions by typing **@brain** followed by your question.
You now have a brain that can answer questions using GPT-4. You can ask your brain questions by typing **@brain** followed by your question.
## Adding GPT-4 Brain to Quivr
To add a GPT-4 Brain to Quivr, you need to perform the following steps:
<Steps>
<Step title="Access the Supabase dashboard">
Log in to your Supabase account and access the dashboard.
</Step>
<Step title="Navigate to the integration table">
Go to the 'integration' table where you can configure your brains.
</Step>
<Step title="Add a custom brain named gpt4">
Add a new entry to the table with the name 'gpt4' to create a custom GPT-4 brain and type `custom`
</Step>
<Step title="Configure the GPT-4 Brain">
Configure the necessary settings for your GPT-4 Brain, including API keys and other preferences.
</Step>
</Steps>