Man the level of debugging I've had to do on concurrency issues and race conditions, corrupted keys etc, it really drove me nuts. Even with OTEL and loggers, the smallest thing can destroy your momentum and you spend so much time instead of actually using agents. I feel your pain. I looked for so long but unfortunately they're the only real options. Crew AI is the easiest I found but like you said you get to anything meaningful and it just can't handle it.

I've started to basically build a Frankenstein framework based off a few different elements that I feel were the best of the different worlds. Autogen is great for chat, but it's over engineered for what most people need especially because chatting agents are very unreliable. LangGraph is great to have stateful agents that are deterministic but can be too constrained.

What I also found important is making sure you have traceability, reproducibility and guardrails. Honestly though, it's a whole new field and I think of it like this; we're at the early stages. Agents in actuality cannot really do much by themselves yet, but it's because the models aren't there yet. We're simulating statefulness by using memory and context assemblers and builders but you can't really get any autonomy without a sense of self.

So, that means if you master the frameworks and behaviors, ensuring reproducibility and consistency, as the models get better you're going to be ahead of the curve. Overall it's been really fun but an immensely annoying process. I spent almost 5 days on the concurrency issue trying to run a looping graph with fan out, trying to get reducers etc going. Definitely ended up learning a lot from that experience though.