---
title: "Comment by Mateo Ruiz on \"How I orchestrate 5 AI agents on a kanban board without writing glue code\" | Hashnode"
description: "The biggest takeaway here isn't the number of agents it's the coordination model. In most multi-agent setups, orchestration complexity grows faster than the age"
url: "https://hashnode.com/posts/orchestrate-5-ai-agents-kanban-no-glue-code/6a01d2b429173e13774891e7/comment/6a69e73188baba8134ccbd6c"
---

[Discussion](https://hashnode.com/posts/orchestrate-5-ai-agents-kanban-no-glue-code/6a01d2b429173e13774891e7)

Comment [How I orchestrate 5 AI agents on a kanban board without writing glue code](https://hashnode.com/posts/orchestrate-5-ai-agents-kanban-no-glue-code/6a01d2b429173e13774891e7)

[Mateo Ruiz](https://hashnode.com/@mateoruiz)

[Jul 29](https://hashnode.com/posts/orchestrate-5-ai-agents-kanban-no-glue-code/6a01d2b429173e13774891e7/comment/6a69e73188baba8134ccbd6c)

The biggest takeaway here isn't the number of agents it's the coordination model. In most multi-agent setups, orchestration complexity grows faster than the agents themselves. Using the Kanban board as shared state and the router as a communication protocol keeps responsibilities explicit and makes failures much easier to debug. The screenshot verification step is another practical idea; evidence-based task completion is far more reliable than trusting an agent's "done" message.
