81–90 of 95 posts
Why is this article on top of HN? this is nothing breaking/new/interesting/astonishing.. The principles are super basic to get the first time you build an agent. The real problem is to get reliability. If you have reliability and clear defined input and output you can easily go parallel. THis seems like a bad 5th class homework
Perhaps because author is perhaps the most prominent agent builder outside of the big labs.
> By using React, you embrace building applications with a pattern of reactivity and modularity, which people now accept to be a standard requirement, but this was not always obvious to early web developers. This is quite a whopper. For one thing, the web started off reactive. It did take a while for a lot of people to figure out how to bring that to client-side rendering in a reasonably decent way (though, I'm sorry…
I was there but I didn't notice reactivity. Maybe we are using two different definitions of reactivity. Do you care to elaborate?
I agree that "It did take a while for a lot of people to figure out how to bring that to client-side rendering in a reasonably decent way".
Earlier quoted context omitted.
The article addresses this specific use under the 'Claude Code Subagents' section. > The benefit of having a subagent in this case is that all the subagent’s investigative work does not need to remain in the history of the main agent, allowing for longer traces before running out of context.
This very narrow very specific single-purpose task-oriented subagent was one of the first things talked about in this every lovely recent & popular submission (along with other fun to read points): What makes Claude Code so damn good (and how to recreate that magic in your agent)!? https://minusx.ai/blog/decoding-claude-code/ https://news.ycombinator.com/item?id=44998295
I'm building a simple agent accessible over SMS for a family member. One of their use cases is finding recipes. A problem I ran into was that doing a web search for recipes would pull tons of web pages into the context, effectively clobbering the system prompt that told the agent to format responses in a manner suited for SMS. I solved this by creating a recipe tool that uses a sub-agent to do the web search and retu…
I'm building a simple agent accessible over SMS for a family member. One of their use cases is finding recipes. A problem I ran into was that doing a web search for recipes would pull tons of web pages into the context, effectively clobbering the system prompt that told the agent to format responses in a manner suited for SMS. I solved this by creating a recipe tool that uses a sub-agent to do the web search and retu…
Are you in USA? How to get around those 10DLC limits on typical SMS/API things (eg Twilio). Or did you go through that process (which seems a lot for a private use-case)
I'm building a simple agent accessible over SMS for a family member. One of their use cases is finding recipes. A problem I ran into was that doing a web search for recipes would pull tons of web pages into the context, effectively clobbering the system prompt that told the agent to format responses in a manner suited for SMS. I solved this by creating a recipe tool that uses a sub-agent to do the web search and retu…
Why are you reinventing the wheel? Just use gpt api with search turned on.
We're in the context engineering stone age. You the engineer shouldn't be trying to curate context, you should be building context optimization/curation engines. You shouldn't be passing agents context like messages, they should share a single knowledge store with the parent, and the context optimizer should just optimally pack their context for the task description.
Is there a framework for this?
Earlier quoted context omitted.
Why are you reinventing the wheel? Just use gpt api with search turned on.
You want to use multiple providers, so if I am not happy with result from gpt, I can switch to perplexity or something else. The power of plug and play is very powerful when you are building agent/subagent systems
Earlier quoted context omitted.
Is there a framework for this?
The best one is google ADK, I must say they are quite thoughful of all the use cases
> By using React, you embrace building applications with a pattern of reactivity and modularity, which people now accept to be a standard requirement, but this was not always obvious to early web developers. This is quite a whopper. For one thing, the web started off reactive. It did take a while for a lot of people to figure out how to bring that to client-side rendering in a reasonably decent way (though, I'm sorry…
> the web started off reactive I was there but I didn't notice reactivity. Maybe we are using two different definitions of reactivity. Do you care to elaborate? I agree that "It did take a while for a lot of people to figure out how to bring that to client-side rendering in a reasonably decent way".