Describe the bug
Models not loading after merge of #106 and #107

Screenshots

Additional context
Vercel is´nt showing any errors in the log, Browser Console is showing this:
Section personalization not found

When I click the button, nothing happens. Imported message templates work fine.

I recently switched from https://github.com/mckaywrigley/chatbot-ui to this repo and tried to import my old conversation history but this only loops the most recent user question and totally misses the answers coming from the assistant. Here is an example:

JSON input:

...
"messages": [
        {
          "role": "user",
          "content": "QUESTION 1"
        },
        {
          "role": "assistant",
          "content": "ANSWER 1"
        },
        {
          "role": "user",
          "content": "QUESTION 2"
        },
        {
          "role": "assistant",
          "content": "ANSWER 2"
        },
...

UI output:

...
QUESTION 2
QUESTION 2
...

Edit:
Streamlined and simplified the example.

Describe the bug
When running the migration script (Generation Script) on supabase I'm seeing this error:

ERROR:  42601: syntax error at or near "NOT"
LINE 121: 	jsonb NOT NULL DEFAULT '{}'::jsonb,

I'll try to figure it out in the meantime.

Trying to deploy on vercel but getting the following error on browser:

Application error: a client-side exception has occurred (see the browser console for more information).

the console has the following erors:

Section personalization not found
Cannot read properties of undefined (reading 'vendor')

This last error seems to be related to model...

env vars defined (Checked correct values):
GOOGLE_CLIENT_SECRET
GOOGLE_CLIENT_ID
NEXTAUTH_URL
NEXTAUTH_SECRET
NEXT_PUBLIC_SUPABASE_URL
NEXT_PUBLIC_SUPABASE_ANON_KEY
SUPABASE_SERVICE_ROLE_KEY
SUPABASE_JWT_SECRET

try adding DEFAULT_MODE and still not working...

Any ideas how to solve this?

Would it be possible to add these model parameter options as well? (Currently it seems to only expose the temperature setting.)

Objective

The project is looking to migrate from NextAuth to Supabase Auth for handling user authentication. This change aims to leverage Supabase Auth's features and streamline our backend services.

Key Deliverables

• Remove NextAuth and integrate Supabase Auth as the sole authentication solution.
• Update all authentication-related code to work with Supabase Auth API.
• Ensure that the authentication flow is fully functional with Supabase Auth, including login, registration, and session management.

Success Criteria

• A seamless authentication experience similar to or better than the current system.
• No regression in performance or user experience.
• Clear documentation on the migration process and changes made.

Contribution Instructions

1. Indicate your interest by commenting on this issue.
2. Fork the repository and create a new branch from the main for this migration task.
3. Implement Supabase Auth, ensuring all features currently using NextAuth are updated accordingly.
4. Perform thorough testing to confirm that the authentication processes are working without issues.
5. Commit your changes and submit a Pull Request with a detailed summary of modifications, including any necessary setup instructions or environment variable changes.

Notes for Contributors

• Prior experience with Supabase Auth is highly recommended.
• Ensure that any sensitive credentials are handled securely and not included in the PR.
• Maintain code readability and adhere to the project’s coding standards.

We appreciate your interest and contributions to this important update for our project. A smooth transition to Supabase Auth will set the foundation for more robust user management and open up new possibilities for our application.

Getting the following error when running locally:

No storage option exists to persist the session, which may result in unexpected behavior when using auth.
If you want to set persistSession to true, please provide a storage option or you may set persistSession to false to disable this warning

Hi Jorge! Great job on this project! It's my favorite way to access GPT-4. One thing that I am missing, however, is the ability to have LaTeX support. It just helps so much with math and makes it much easier to view.
Thanks!

Describe the bug
I´m getting a 404 NOT_FOUND when I´m getting auto redirected to /de. When I type /en manually everything is working fine.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'https://app.unsaged.com/de'

Screenshots

Describe the bug
Add AWS Bedrock to unsaged

Describe the bug
When I login I got stuck to the loading screen "Loading Conversations..."
Console is showing the error "Section personalization not found"

Screenshots

Desktop (please complete the following information):

• OS: Windows
• Browser chrome
• Browser version latest

Kindly am requesting whoever has used this if u are not getting abnormal open ai charges, am having fear of using my api here despite the goodness of unsaged

Describe the bug
For any reason I´m getting the following error when using GPT-4. After 4-5 Messages I´m getting a rate limit error on the server. Any idea why this is coming?

Additional context
{
message: 'Rate limit reached for gpt-4 in organization ***** on tokens per min. Limit: 10000 / min. Please try again in 6ms. Visit https://platform.openai.com/account/rate-limits to learn more.',
type: 'tokens',
param: null,
code: 'rate_limit_exceeded'
}

Hi there! First off, thanks for building this project! It's super cool and I'm using it extensively <3

I'm planning to roll this out to some colleagues at my organization and ran into an issue. In my case we have a few different environment variables provided with API credentials so that we have a number of models users can access.

I've set the environment variable NEXT_PUBLIC_DEFAULT_MODEL to the specified model I'd like to use as the default (gpt-4-32k), but the setting doesn't appear to be respected. The same is true for NEXT_PUBLIC_DEFAULT_TEMPERATURE when set to 1, which is the default value ChatGPT uses and what I'd like to default temperature to for my users.

Any ideas what I may be doing incorrectly here? Thanks again! <3

Several useful OpenAI models are missing from the types. For example gpt-3.5-turbo-16k as well as the dated models.

Kindly can u update this including gpt-3.5-turbo-16k-0613

I added everything it my .env.local and started the script but I end up with a black screen with the url and can't login
http://localhost:3000/api/auth/signin?callbackUrl=%2F

App works fine locally but on Vercel the chat only returns the first string and freezes. Is there a different configuration or something that am I missing for vercel?

Thanks!

Sometimes I like to spin up different ollama servers for testing so I thought it would be nice to have a settings page that lets you set the ollama url so you don't have to edit the .env.local and redeploy.

Not sure if anyone would find that useful but figured I would put it out there. Also nice for when you forget to set it in the .env as well.

Hi Jorge,

I encountered an issue with the latest build: it compiles and runs in Docker, but accessing the server only loads the database and conversations partially before showing a blank page. No login screen appears. The logs indicate all models as "Not implemented."

Could this be a configuration miss on my end or a bug in the code?

Thanks for your help,

Mario

It seems whenever I start a new conversation, the temperature is reset to 0.7, and there is no way to save a custom default or persist the current value between conversations?

The Supabase generation script on the getting started page is currently this but it should be this one.

Apparently there was a name change or something and the original link is no longer up to date.

I added everything it my .env.local and started the script but I end up with a black screen with the url and can't login
http://localhost:3000/api/auth/signin?callbackUrl=%2F

Image generation will be or was added in PR #122.
There are still some optimizations needed:

• Update styles to make the image smaller and more responsive
• Optional persist image on supabase (url return is only available for aber 1 or 2 hours)
• Add additional params for Dall-E
• Update ai.models.ts to reflect the correct settings for dall-e 2/3
• Remove the image modules from the system_prompt modals
• Add documentation

Current Example:

npm dependency issue on vitest
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Follow the Installation Guide https://unsaged.com/docs/getting-started/installation
2. When running "npm i" in ~/unSAGED/apps/unsaged, error reported as follow

# npm resolution error report 

While resolving: [email protected]
Found: [email protected]
node_modules/vitest
  dev vitest@"^1.0.4" from [email protected]
  apps/unsaged
    [email protected]
    node_modules/unsaged
      workspace apps/unsaged from the root project
  peer vitest@"^1.0.0" from @vitest/[email protected]
  node_modules/@vitest/browser
    peerOptional @vitest/browser@"^1.0.0" from [email protected]
  peer vitest@"^1.0.0" from @vitest/[email protected]
  node_modules/@vitest/ui
    peerOptional @vitest/ui@"^1.0.0" from [email protected]

Could not resolve dependency:
peer vitest@">=0.30.0 <1" from @vitest/[email protected]
node_modules/@vitest/coverage-c8
  dev @vitest/coverage-c8@"^0.33.0" from [email protected]
  apps/unsaged
    [email protected]
    node_modules/unsaged
      workspace apps/unsaged from the root project

Fix the upstream dependency conflict, or retry
this command with --force or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.

Screenshots

Desktop (please complete the following information):

• OS: Debian 12

Additional context
Running "docker build -t unsaged -f apps/unsaged/Dockerfile . --rm" in ~/unSAGED hung as well.

I imported a json that I had exported from chatbotui.com, but the app now throws this error when run

Thanks for making this very useful ChatGPT frontend!

But I only see a button to import data.

How to export all data as json? :)
(Especially the custom prompts & system prompts.)
So that it can be edited and re-imported later.

Can you help me to add the email + password as a auth provider ?
from what i was able to do is to only do it with SSO like google + github
but how can i do to add for email and password using supabase auth ?

Thanks for your help

Hi,

I'm using a docker self-hosted install of supabase. have done the setup, created a user with email address in supabase and connected unsaged with all the Keys to the supabase instance.

I can login via email authentication, will get redirected back to unsaged and I'm getting a black screen.
It looks like I'm getting a 401 on trying to get to the conversation resource.

Do I need to assign the supabase user to these tables, or maybe there needs to be an project API key defined in the unsaged config ?

I used the generation script
https://github.com/jorge-menjivar/unSAGED/blob/dev/packages/unsaged/db/GenerationScript.sql
via the SQL Editor.

Thanks for any advise.

I think it would be great to create a develop branch and maybe stick to something like Gitflow so each update can be created in a feature branch, will be merged and tested in develop and then is merged working in main.

Goal

The objective is to extend our authentication capabilities to include Clerk as an alternative to Suppabase. This integration should allow for seamless switching between the two services through environment variable configurations.

Requirements

• Complete #91 first
• Integrate Clerk alongside Suppabase in the authentication flow.
• Ensure that the authentication helpers are adaptable for use with both Supabase Auth and Clerk.
• The switch between Supabase Auth and Clerk should be manageable by setting the appropriate .env variables.
• Document the changes comprehensively in a single feature branch PR.

Expected Outcome

A successful contribution will result in a flexible authentication setup where either Supabase Auth or Clerk can be used interchangeably based on simple environment variable toggles, without affecting the existing authentication functionality.

Contribution Process

1. Express your interest by commenting on this issue to prevent overlapping work.
2. Fork the repository, and create a feature branch for this task.
3. Implement the integration while ensuring that both authentication systems can coexist and are selectable via .env variables.
4. Thoroughly test the implementation to ensure that both systems work independently when chosen.
5. Open a Pull Request with a detailed list of changes and testing procedures for review.

Additional Notes

• The implementation should not break the current default authentication method.
• Keep changes minimal and modular to facilitate easy review and potential rollback.
• Ensure backward compatibility for existing users who might not switch to Clerk immediately.

This feature is critical for users who prefer Clerk or require its specific functionalities, and your contributions towards this dual authentication capability will significantly enhance the flexibility of our application.

Thank you for considering this contribution; we are excited to see your innovative solutions!

When running locally I'm seeing this error

./utils/app/auth/providers.ts:97:27
Module not found: Can't resolve '@/node_modules/next-auth/providers/email'
   95 |   }
   96 |   if (EMAIL_FROM) {
>  97 |     const provider = await import('@/node_modules/next-auth/providers/email');
      |                           ^
   98 |     const EmailProvider = provider.default;
   99 |     providers.push(
  100 |       EmailProvider({

https://nextjs.org/docs/messages/module-not-found

Import trace for requested module:
./app/api/auth/[...nextauth]/route.ts

In order to build the project I'm adding npm i into the Dockerfile. Otherwise this doesn't work on a host without npm.
This approach worked yesterday.

# ---- Dependencies ----
FROM base AS dependencies
RUN npm i
RUN npm ci

Today looks like it's breaking when I get the latest version form main.

npm notice
npm notice New major version of npm available! 9.6.3 -> 10.2.4
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.2.4>
npm notice Run `npm install -g [email protected]` to update!
npm notice
npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported URL Type "workspace:": workspace:*

npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2023-11-23T11_47_26_971Z-debug-0.log

I can see commits have been made to the package.json file.

Maybe this could be incorporated as a Feature Enhancement ?

https://help.openai.com/en/articles/8555545-file-uploads-with-gpts-and-advanced-data-analysis-in-chatgpt

https://community.openai.com/t/send-an-image-file-via-the-api-from-a-url-with-xano/521146

i18n will be or was fixed in PR #128.
There are still some optimizations needed:

• Add all previous languages to the new translation structure

Translation will be managed via localazy https://localazy.com/p/unsaged

I noticed using unsaged.com does a lot of API requests even with very short conversations which shouldn't cost as much. I can see $0.10 increase after 10-30 mins of having used the tool (1 or 2 messages only).

Hi, I'm trying to setup the google auth SSO using supabase:

but when i click on the login button i got redirect to this url:
https://xxxxxxxxx.supabase.co/api/auth/signin/google

with an error message saying : {"message":"No API key found in request","hint":"No apikey request header or url param was found."}

my env file look like this:

OPENAI_API_KEY=xxxx
NEXT_PUBLIC_AUTH_ENABLED=true

NEXT_PUBLIC_SUPABASE_URL=https://xxxxxxx.supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=xxxxxxxx

SUPABASE_SERVICE_ROLE_KEY=xxxxxxx
SUPABASE_JWT_SECRET=xxxxxxxxxx
NEXTAUTH_SECRET=xxxxxxxx
NEXTAUTH_URL=https://xxxxxx.supabase.co

GOOGLE_CLIENT_ID=xxxxxxx-xxxxxxxx.apps.googleusercontent.com
GOOGLE_CLIENT_SECRET=xxxxxxxx
GOOGLE_API_KEY=xxxxxxxx

Expose the next_auth schema
Expose the next_auth schema in the API settings by adding next_auth to the "Exposed schemas" list.

More information here.

Then copy the output and save it for the next step.

API settings don't exists in the UI in a self hosted instance.

Overview

We aim to implement a custom sign-in page compatible with the new /app structure in Next.js. The current documentation for NextAuth.js appears outdated and doesn't align well with the latest Next.js updates, leading to integration issues.

Objective

Successfully migrate the authentication flow to utilize a custom auth/signin page, replacing the default one provided by NextAuth.js. This page should be fully functional and modifiable according to our project's requirements.

Current Behavior

The default sign-in page provided by NextAuth.js is currently in use, as attempts to implement a custom page have not been successful.

Encountered Issues

While attempting to set up the custom sign-in page, I ran into several problems that I believe might require a more in-depth look, possibly from one of the project's paid contributors.

Request for Contribution

We are looking for contributors who can take on this task. If you have experience with Next.js and NextAuth.js, especially with the new /app structure, your expertise would be highly valuable.

Steps to Contribute

1. Leave a comment if you're interested in tackling this issue to avoid duplicate efforts.
2. Fork the repository and set up the project locally.
3. Make the necessary changes to integrate a custom sign-in page with NextAuth.js.
4. Test the functionality to ensure compatibility with the /app structure.
5. Submit a Pull Request with a detailed description of your changes.

Definition of Done

• The custom auth/signin page is implemented and functional.
• Compatibility with the latest Next.js /app structure is confirmed.
• The page can be easily modified for further customization.

Your contributions are greatly appreciated, and we look forward to collaborating on this enhancement!

Title says it all. The readme says it defaults to GPT-3.5-Turbo but in my case it threw an error. When I defined it explicitly it worked fine.

Error: Error serializing .defaultModelId returned from getServerSideProps in "/".
Reason: undefined cannot be serialized as JSON. Please use null or omit this value.

When using google auth what do we use as the redirect url?

Hi Jorge
Thanks for the excellent work.
I follow all the steps to get unSAGED running on Docker but it get stuck on Initializing database

https://chatbot.digitaldevices.ca/
The docker log don't give much information.
_unsaged_logs.txt
The supabase logs show some requests
supabase_logs.csv
But I can't figured out the issue.
Do you have any idea what the problem is?
Thanks

unSAGED does not seem to identify the code blocks correctly for vba code.

It looks to use \begin{code} and \end{code} which is not recognized maybe?

See attached screenshot of the issue

Describe the bug
Add GPT 4 Vision https://platform.openai.com/docs/guides/vision

I've followed the 7 steps in readme, mapping a /etc/host dns name for the application and using it in .env.local

• Application loads OK
• Google authentication finishes OK (no errors after login, row in next_auth schema tables, browser redirects)
• Browser redirects to http://thedomainiveconfigured:3000/es
• Infinite redirect loop

Any clue?

Thanks you for your project

If I create a new system prompt, it shows in the list of system prompts but doesn't populate the menu on the right, which continues to only offer the default prompts.

Describe the bug
When using Ollama server and a Vercel deployment I´m running into some timeouts

Screenshots

Error
Error: Your function was stopped as it did not return an initial response within 25s

Additional context
Ollama server running on Hetzner Cloud with a Nginx Proxy Manager in front to proxy the ollama server to https and enable Access Lists for HTTP Basic Auth

More information on: #47 and #73

Result:
Multiple language redirect should work.