ffacu

3 ms·

1. 1.▲
   Agents Declaration – Designing an Agents Orchestration Library – Part II(ffacu.dev)

   2 points by ffacu 3mo ago|0 comments
2. 2.▲
   Workspace, Runtime, and Directories – Designing an Agent Orchestration Library(ffacu.dev)

   2 points by ffacu 3mo ago|1 comments
3. 3.▲
   by ffacu 3mo ago

   Part I: Workspace, Runtime, and Directories Most tools I tried dumps all the agents into one workspace. Here's the structure I went with instead. Note: I tried after writing this the Kilo extension on VS Code, which partly does the wor
4. 4.▲
   by ffacu 4mo ago

   I very much agree with you. But the value of an orchestrator still seems to exist, just not as another step before claude code. I think the correct role of an orchestrator is not what most libs seem to be doing: having the "manager&quo
5. 5.▲
   by ffacu 4mo ago

   I have discussed this already, and was referred to solutions like Agno or Google SDK or other libraries. But there I don't find anything that makes me think "this is better than just having 4 terminals splitted in my pc and toggli
6. 6.▲
   I don't see any good orchestration system for AI agents(ffacu.dev)

   3 points by ffacu 4mo ago|4 comments
7. 7.▲
   by ffacu 4mo ago

   I think that this is becoming increasingly true only for large, well-known repositories, where the maintainers have a lot to lose by doing anything shady. I don't think the React team could get away with doing something like that, for