The Board Is Read-Only, and That's the Point
Every other Kanban board trains you to drag cards around. The agent board refuses — because dragging a running card would either lie to you or kill it.
Every Kanban tool you've ever used has trained you the same way: cards live in columns, and you move them by dragging. It's such a deeply ingrained interaction pattern that a board which looks like a Kanban board and doesn't let you drag anything reads, at first glance, like a bug. In Piskes's agent Board, it isn't. It's a deliberate refusal, and the reasoning behind it is worth knowing before you go looking for the drag handle.
What the board actually is
The Board assembles four lanes from state that already exists — pulled together from three other screens: Schedules, Chat, and Approvals — and groups it by bot rather than by an arbitrary column a person assigned by hand. It's a real-time view of what your agents are actually doing, not a planning surface where you arrange intentions.
That distinction is the whole reason it doesn't accept drags. The header comment on the page states the logic directly: there's nothing on this board a person can move by hand, because a run is running because it is running — not because someone decided to place it in a column labeled "in progress." Dropping its card into a column labeled "done" wouldn't record a decision the way it would on a normal Kanban board; it would either falsely claim the run finished when it hasn't, or it would have to actually kill the run to make the card's new position true. Neither of those is what a drag gesture on a normal board is supposed to mean, and building either behavior in to satisfy the expected interaction would have made the board a liar in one direction or a blunt instrument in the other.
Why refusing the familiar gesture is the more honest choice
It would have been easy to make the board draggable anyway, just to match what everyone expects a Kanban-shaped screen to do — and it would have quietly turned an honest status view into something that could either mislead you about what actually happened or take a destructive action disguised as a UI convenience. Refusing that is a small design decision with an outsized amount of trust behind it: this is a screen you can look at and believe, precisely because it never lets you pretend a running thing is finished just by dragging its card somewhere else.
If you open the Board expecting to rearrange it, the flat refusal to be dragged is worth reading as a feature, not a limitation. It's a status board doing exactly one honest job: showing you what's true.