swrly

3 ms·

1. 1.▲
   by swrly 6mo ago

   This is a great question. We handle it with session state that persists across turns — the agent's memory scope can be set to "agent" (persists across runs) vs "swirl" (one run only). For truly long-running conversa
2. 2.▲
   by swrly 6mo ago

   Parallel workers in git worktrees is clever. We have a similar pattern with fan-out/fan-in — you can split an array across parallel agent executions and collect results. The SQLite-structured JSON output approach is interesting for coo
3. 3.▲
   by swrly 6mo ago

   Interesting — I hadn't looked into AGNO closely. The isolation and control plane approach sounds solid. How do you handle observability? That's been one of the harder parts for us — knowing exactly which agent produced which outpu
4. 4.▲
   Ask HN: How are you orchestrating multi-agent AI workflows in production?

   8 points by swrly 6mo ago|11 comments
5. 5.▲
   by swrly 6mo ago

   I agree, YouTube search is completely useless when we really need it. Especially with fizzy search!