[HN Gopher] Llama-agents: an async-first framework for building ...
___________________________________________________________________
Llama-agents: an async-first framework for building production
ready agents
Author : pierre
Score : 85 points
Date : 2024-06-28 16:54 UTC (6 hours ago)
(HTM) web link (github.com)
(TXT) w3m dump (github.com)
| cheesyFish wrote:
| Hey guys, Logan here! I've been busy building this for the past
| three weeks with the llama-index team. While it's still early
| days, I really think the agents-as-a-service vision is something
| worth building for.
|
| We have a solid set of things to improve, and now is the best
| time to contribute and shape the project.
|
| Feel free to ask me anything!
| haidev wrote:
| Is this k8s for LLMs?
| CaptainOfCoit wrote:
| The submitted project is a framework for building programs.
| Kubernetes is a platform for deploying and running
| applications. So no.
| cheesyFish wrote:
| Not quite. More like a framework to make LLMs/agents easier
| to deploy in a distributed fashion. We have a PR that shows
| how to deploy this with k8s!
| EGreg wrote:
| What do you think of this, given that LangChain failed:
|
| https://engageusers.ai/ecosystem.pdf
|
| We're building this -- do you think it's worthwhile, and what
| advice would you give?
| isoprophlex wrote:
| How about we ask the AI how it feels?
|
| RIP in peace, VC money
|
| https://chatgpt.com/share/f287f9aa-d5c8-4866-a5f0-65499079d5.
| ..
| gknoy wrote:
| alright, let's shred this ... to pieces. the layout
| --goddamn, where's the flow? it's a cluster-
|
| I am amazed that the LLM uses language like this. Is it
| mainly because of the tone of the prompt? I'm both
| surprised that it's allowed to do that, and amazed that it
| did it well. O_O
| ramon156 wrote:
| Ah yes, AAAS
| cheesyFish wrote:
| maybe agent micro-services is a better way to frame it ha
| k__ wrote:
| I have yet to see a production ready agent.
| cheesyFish wrote:
| It's definitely tough today, but its just a matter of a) using
| a smart LLM b) scoping down individual agents to a manageable
| set of actions
|
| As more LLMs come from companies and open-source, their
| reasoning abilities are only going to improve imo.
| k__ wrote:
| I hope this will improve.
|
| Right now the products I see are just junior level software
| with an LLM behind.
| m_a_u wrote:
| For me it's a difficult field. The thoughts "I could have
| written this myself, but maybe better" and "I will never
| understand this" occur with similar frequencies
| ldjkfkdsjnv wrote:
| 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/
|
| 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 wrote:
| I 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.
| williamdclt wrote:
| I must be missing something: isn't this just describing a queue?
| The fact that the workload is a LLM seems irrelevant, it's just
| async processing of jobs?
| lawlessone wrote:
| everything's a queue in software if you think about it :-). But
| does sound more like queue than most things
| soci wrote:
| or a stack!
| cheesyFish wrote:
| It being a queue is one part of it yes. But the key is trying
| to provide tight integrations and take advantage of agentic
| features. Stuff like the orchestrator, having an external
| service to execute tools, etc.
| conceptme wrote:
| It does not sound very specific "stuff" like the
| orchestration, any other queues needs to deal with assigning
| work?
| jondwillis wrote:
| why use already overloaded "llama"
___________________________________________________________________
(page generated 2024-06-28 23:00 UTC)