Live data from Hacker News

Show HN: Next.js ChatGPT – Responsive chat application powered by GPT-4

github.com

1–10 of 36 posts

Re: Show HN: Next.js ChatGPT – Responsive chat application powered by GPT-4

#3

What does it take to make a basic ChatGPT-like frontend, with code highlighting, run in sandbox, drop-files, and 'acting' in prompts? Clone away and enjoy. First time poster

Thanks, it is good :) You don’t need the serverside though; you can just call openai apis straight from the client. Makes things easier!

Re: Show HN: Next.js ChatGPT – Responsive chat application powered by GPT-4

#5

What does it take to make a basic ChatGPT-like frontend, with code highlighting, run in sandbox, drop-files, and 'acting' in prompts? Clone away and enjoy. First time poster

Thanks, it is good :) You don’t need the serverside though; you can just call openai apis straight from the client. Makes things easier!

It seems to support both? First it tries to load the key from a environment variable, and if it cannot, it'll ask for it client-side.

None the less, if you're building a project for others, you most likely don't want the secret key to be public, which it'd be if you embed it in the client-side code.

Re: Show HN: Next.js ChatGPT – Responsive chat application powered by GPT-4

#6

What does it take to make a basic ChatGPT-like frontend, with code highlighting, run in sandbox, drop-files, and 'acting' in prompts? Clone away and enjoy. First time poster

What do you mean by “acting”?

That it pretends to be a Scientist? Or that it can perform actions (like sending an email or searching the web)?

If the latter, do you have more info/docs about it? Didn’t see it on the roadmap.

Re: Show HN: Next.js ChatGPT – Responsive chat application powered by GPT-4

#9

Earlier quoted context omitted.

Thanks, it is good :) You don’t need the serverside though; you can just call openai apis straight from the client. Makes things easier!

It seems to support both? First it tries to load the key from a environment variable, and if it cannot, it'll ask for it client-side. None the less, if you're building a project for others, you most likely don't want the secret key to be public, which it'd be if you embed it in the client-side code.

> It seems to support both?

Ah, only saw the api one!

Post reply on HN