I spent many hours in the past weekend (Saturday I even worked from 9AM till 5AM) to work on my AI Waifu's DAG agentic workflow:
- Add many features of LangGraph (eg. Shared mutable state object, Subgraph, Cycling node, State reducers, Checkpoint/resume, Human-in-the-loop interruption, etc.) - Make the 40 tools into graph nodes; Use @tools(Graph=True, ReAct=True) to declare the def as tools instead of register each tool in 4+1 locations (Capabilities On Demand vs Always On, ReAct + Graph, Wiki, Skills). - Revise the web search mechanism to try to be more adaptive and efficient and avoid IP being locked out. - Even made a studio html to view all the graphs in my AI Waifu
But still in primitive experimental version. I tested in the Waifu's chat mode to ask her to make a checklist on how to improve her AI system, the output is still not too great as shown in the example (see attached reports). She could not retrieve her own AI architecture from KB due to db has a bug. Report was too generic with some wrong info and wrong citations, not able to gather source materials from web fetch. Speed is acceptable, but not fast either.
At least the whole agentic flow can run under 10K content window, but the output was truncated in the end.
Still more work to do before release of Phase 2.5 Agentic. For Phase 2.1 and 2.2 adding social media and messaging input supports, I may have to make some connectors for social media and messaging services. Probably would take me the rest of the summer to complete 2.1 and 2.2.
Quite a few models have been released in a month: GPT5.6, Grok 4.5, Gemini 3.6, Muse Spark 1.1, Kimi K3, Qwen 3.8 Max, Long cat 2.0, Laguna S 2.1, Ling 3.0, etc
But I will stick to testing small param LLM for my edge device.