Live data from Hacker News

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

github.com

31–36 of 36 posts

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

#31
post #27

Earlier quoted context omitted.

Nice. How would you go about providing a dynamic list of delgates? Could it work to just give one delegate that can provide a list of delegates with a description of the actions they can perform (then that delegate can query a db and return a list)? Re-reading, I’m guessing the prompt could also be dynamically generated to include the most relevant delegates.

At that point we're basically back to the `AI is just nested if-else expressions` story. The only difference is that now there is a language reader on top that understands the semantic of your language. But actors (or agents in LangChain lingo) are just if-else. The tools you connect them to must be developed separately.

Sure, you could also say that human language/action capacity is just a biological LLM with some ifs on top that give it access to actions.

In the case you describe, you can have an LLM write the tools.

Yes, the first tools and bridge code might need to be manually built. But after that it could be LLMs all the way down.

Kind of similar to writing a new programming language. At first you write it in another language but after compiling it for the first time, you can then write the language in the language itself.

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

#33

Earlier quoted context omitted.

It seems like it's setting gpt-4 here as well: https://github.com/enricoros/nextjs-chatgpt-app/blob/466a366... But come on, read through the source, look for the issue, I'm sure you can track down at least something :)

Sorry, as soon as posted my comment, I looked again and found the other occurrence. It's quite late here and I just followed your advice blindly :) Works now.

Hey guys, op here. Merged the PR for 3.5-Turbo support and cleaned up the code (very good observations on all the places 'gpt-4' was hardcoded). Combo box to select the model. GPT-4 will need a 4-enabled key, while 3.5-Turbo will work with any GPT key.

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

#34
post #17

Earlier quoted context omitted.

There seems to be already a PR for adding 3.5 support. The community and speed of change in this field is mind blowing!

Oh yeah, changing 33 lines is truly revolutionary!

OP: I went to sleep with this as my 1st post and 1 star, and woke up with a PR for 3.5-Turbo pending. Community for the win!

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

#35
post #4

nice, maybe you can make the initializing prompts in https://github.com/enricoros/nextjs-chatgpt-app/blob/main/pa... transparent to the user and even changeable by them.

When the user selects one of those, any query will reveal the prompt. Can be changed but the change won't be persisted yet. We added a 'Custom' preset today that requires editing. Agree with your point tho - rn editing happens via 'forking' :)

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

#36
post #27

Earlier quoted context omitted.

Nice. How would you go about providing a dynamic list of delgates? Could it work to just give one delegate that can provide a list of delegates with a description of the actions they can perform (then that delegate can query a db and return a list)? Re-reading, I’m guessing the prompt could also be dynamically generated to include the most relevant delegates.

At that point we're basically back to the `AI is just nested if-else expressions` story. The only difference is that now there is a language reader on top that understands the semantic of your language. But actors (or agents in LangChain lingo) are just if-else. The tools you connect them to must be developed separately.

Very good point. Once you start breaking down a llm into presets/delegators, you introduce basically if-else, with all the problems of that split. Lack of visibility, local vs global optimization, lack of control and predictability, asymmetry of information. I wonder if the current Agents approach is a stopgap solution.
Post reply on HN