Agent engineering moves faster than anyone can read.
So I built an agent to keep up:
📄 new research papers
🛠️ engineering blogs from top labs
🧵 posts from the best builders
I turn the best into a 30-min podcast with two AI hosts.
This is AgentsPod: https://t.co/PXtZP0suuO
Sorry this isn’t answering your question - but a big part of model behavior is determined by model training - and sometimes we simply are at the mercy of what’s important to the labs. So the memory retreival patterns and such may not be meeting your expectations until models are trained well on this.
@JoshARosen Agreed - I also notice agents like brute forcing its way into finding information rather than starting narrow and widening the search. This happens to me for example if the agent is trying to get some info from a storage bucket where it will try to traverse every folder.
How are people managing context for different projects when using coding agents? I maintain a second brain that I can't work without at this point but see a lot of folks who don't have one.
For people who run several claude code terminals at the same time working on different things - how do you maintain the code quality and engineering bar?
@pauliusztin_ Yeah - we should use multi agent is to offload and manage context wisely by letting other agents "explore" and return only relevant context back.
@birk Building great cli for every resource/service. Enables lots of things like verification loops, context fetching, automating workflows etc. Turns out llms know how to use clis very well.
@yongfook Agreed - we are already seeing this in software engineering as well - there is complete AI SDLC where the human engineer’s job is to meet with people, get the requirements, get the business context etc as input to the agents who then deliver it e2e. Code seems solved.
@hwchase17 I don't believe so - as models get better - skills will be absorbed in the models training i.e llms will get better at common workflows - but memory will stay outside the models' weights so memory != skills.
@ShivamPatxl Thanks - but I’m talking about the step before that - the architecture design, code design etc. codex will only review what claude has written from a “finding bugs” perspective. Does it review whether the code can scale, factor in business logic etc?
Full episode (32 min), with chapters and every source:
https://t.co/4GEAOS6vOi
I dig into the stories and shape every episode, with AI as my co-producer. Follow along for more.
Same AI model. Can Bölük (@can1357), security researcher, changed only how his agent edits files. Success rate: 6.7% → 68.3%.
The model wasn't the problem. The tooling around it was.
Episode 1 of AgentsPod, my podcast on building with AI agents 🧵
Nicholas Carlini at Anthropic had 16 Claude agents build a C compiler. His biggest lesson: the tests that verify the agent's work have to be nearly perfect.
Easy way to check yours: break the code on purpose and see if your tests catch it.
https://t.co/Zs11tT9jdc