chandureddyvari
Joined 7 years ago
Joined 7 years ago
It's not like they're trying, they are trying very hard
What worked for me was to ask Astra/Fable to include pseudo code in the design doc. which comes to 1-2 pages. Easy for me to skim and change the direction/approach. Rest all of the flowery language is for LLM giving context.
IMO Fable 5.1 ~ Astra > GPT 5.6 Sol > Opus.
Another thing i discovered is less is more (in case of skills as well)., don’t add lots of skills., keep them very handful - I’ve got 9 skills so far (many people have 100s installed from marketplaces and plugins)
I can see this becoming much more useful once the docs get heavier: large PDFs, XLSX files, images, etc. At that point you probably need embeddings, reranking etc. But I think agents are smart enough to write scripts to retrieve what they want if we run them on a sandbox(which we are trying to do currently). bookmarking this for now.
Good write-up though!
Is this equivalent of DAGs for sub agents inside claude code? Can i pause and resume/retry workflows? How stateful are they?
Really appreciate it someone claude code can throw more light on above. I’m trying to see if I can get langgraph equivalent DAGs here.
Similar sentiment shared with other startup founders- check on x about all VCs talking about moats against big labs.