Alternatives
Products that do what Trello Boards for Agents does
Most agent tools (Devin, n8n, Codex, etc.) create new user experiences and dashboards for managing work. It feels like we should work alongside agents and use the tools we already do. To test this experience, we built Dispatch Board. It lets you work alongside agents and humans using a kanban board to create tasks and respond to any questions that come up. Would love feedback on workflows you’d try, where it breaks, or whether this belongs inside an existing tool instead of yet another board. Thanks!
- 1VC
Agent Kanban has 4 main features: GitOps & team friendly kanban board integration inside VS Code Structured plan / todo / implement via @kanban commands Leverages your existing agent harness rather than trying to bundle a built in one .md task format provides a permanent (editable) source of truth including considerations, decisions and actions, that is resistant to context rot
Mar 2026 · appsoftware.com
- 2VK
Hey HN! I'm Louis, one of the creators of Vibe Kanban. We started working on this a few weeks ago. Personally, I was feeling pretty useless working synchronously with coding agents. The 2-5 minutes that they take to complete their work often led me to distraction and doomscrolling. But there's plenty of productive work that we (human engineers) could be doing in that time, especially if we run coding agents in the background and parallelise them. Vibe Kanban lets you effortlessly spin up multiple coding agents. While some agents handle tasks in the background, you can focus on planning…
2025 · github.com
- 3
- 4
- 5
- 6KB
2025 · github.com
- 7CO
We recently started to use agents to update some documentation across our codebase on a weekly basis, and everything quickly turned into cron jobs, logs, and terminal output. it worked, but was hard to tell what agents were doing, why something failed, or whether a workflow was actually progressing. We thought it would be more interesting to treat agents as long-lived workers with state and responsibilities and explicit handoffs. Something you can actually see and reason about, instead of just tailing logs. So we built Clawe, a small coordination layer on top of OpenClaw that lets agent…
Feb 2026 · github.com
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15RT
This project (Agents Observe) started as an exploration into building automation harnesses around claude code. I needed a way to see exactly what teams of agents were doing in realtime and to filter and search their output. A few interesting learnings from building and using this: - Claude code hooks are blocking - performance degrades rapidly if you have a lot of plugins that use hooks - Hooks provide a lot more useful info than OTEL data - Claude's jsonl files provide the full picture - Lifecycle management of MCP processes started by plugins is a bit kludgy at best The biggest takeaway is…
Apr 2026 · github.com
- 16
- 17
- 18
- 19
- 20KC
Hello HN, Ever since agents have become increasingly common in development, I've been scratching my head as to how to control their randomness. Recently, I decided to emulate an issue-tracking and project-management tool for agent-driven workflows. Kanban is a Rust-based coordination layer designed to provide a feature-rich terminal interface and enforce rigorous workflows. It aims to be versatile and extendable, made to be tailored to any preferred flow. It comes with full git integration and guardrails such that only what truly benefits a project can go through. The workflow boils down to…
May 2026 · codeberg.org
- 21
- 22
- 23OA
We were both genuinely impressed by Claude Code after it helped each of us fix nasty CI problems overnight. Doing those fixes manually would have taken days. After that experience, we each found ourselves struggling through Ctrl+Tab through multiple Claude Code windows in our terminals. While we enjoyed having agents working for us in parallel, context switching and cycling through each terminal tab was a real pain. So we thought: Can we design a TUI dashboard that manages a large swarm of agents in one place? Even better, can agents manage agents hierarchically, like how companies work?…
May 2026 · omar.tech
- 24KM
I built kanban-md because I wanted a simple local task tracker that works well for the agent loop: drop tasks in, run multiple agents in parallel, avoid collisions, and observe progress easily. Tasks are just Markdown files (with YAML frontmatter) in a `kanban/` next to your code — no server, no DB, no API tokens. Simple, transparent, future-proof. What makes it useful for multi-agent workflows: - *Atomic `pick --claim`* so two agents don’t grab the same task. - *Token-efficient `--compact` output* (one-line-per-task) for cheap polling in agent loops. - *Skills included* -- just run…
Feb 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →