4 ms·
These types of frameworks will become abundant. I personally feel that the integration of the user into the flow will be so critical, that a pure decoupled back
by ldjkfkdsjnv 2y ago
These types of frameworks will become abundant. I personally feel that the integration of the user into the flow will be so critical, that a pure decoupled backend will struggle to encompass the full problem. I view the future of LLM application development to be more similar to:
https://sdk.vercel.ai/ https://sdk.vercel.ai/
Which is essentially a next.js app where SSR is used to communicate with the LLMs/agents. Personally I used to hate next.js, but its application architecture is uniquely suited to UX with LLMs.
Clearly the asynchronous tasks taken by agents shouldnt run on next.js server side, but the integration between the user and agent will need to be so tight, that it's hard to imagine the value in some purely asynchronous system. A huge portion of the system/state will need to be synchronously available to the user.
LLMs are not good enough to run purely on their own, and probably wont be for atleast another year.
If I was to guess, Agent systems like this will run on serverless AWS/cloud architectures.
- cheesyFish 2y agoI agree on the importance of letting the user have access to state! Right now there is actually the option for human in the loop. Additionally, I'd love to expand the monitor app a bit more to allow pausing, stepwise, rewind, etc.
- afro88 2y agoHard agree. The user being part of the flow is still very much needed. And I have also had a great experience using Vercel's AI SDK on next.js to build an LLM based application