Karavan turns Trello into agent workflow engine

Karavan’s real hook is not “yet another agent framework” but a pragmatic orchestration design that replaces a pile of infra with a tool many teams already understand.

• –Trello-as-infrastructure removes the usual database, Redis, and vector-store overhead, which makes the system unusually inspectable for a multi-agent setup
• –The worker abstraction is thin and config-driven, so coder, reviewer, planner, and researcher roles are mostly different runtime settings rather than separate agent classes
• –Multi-board routing gives teams a flexible way to split coding and research pipelines without hardcoding a rigid DAG
• –The model-agnostic roadmap matters because it keeps Claude from being the core dependency and makes local-model support a plausible community contribution
• –The tradeoff is scale and robustness: leaning on Trello and Telegram is elegant for small teams and experiments, but it is still a SaaS-centric control plane rather than hardcore production infra