Show HN: VS Code Agent Kanban: Task Management for the AI-Assisted Developer (appsoftware.com)
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
34 comments
[ 4.4 ms ] story [ 65.0 ms ] threadInteresting to see the Kanban workflow being adapted to managing agents, makes sense; each item having the same UX as a Github Issue.
It reminds me of how Zed wants to have built in Slack when it will be impossible to get everyone to use Zed. A feature that can never really materialize because developers get a say in their tools
Furthermore, an existing kanban (ticket) workflow will expect you to refine the context into something more ... concentrated, or at least something that we are used to seeing as developers working with tickets, at least more so than the chat history that seem to be favored.
Have you put any thought into how this would integrate into such a process?
Youtube (Quick demo): https://www.youtube.com/watch?v=Y4a3FnFftKw
GitHub: https://github.com/appsoftwareltd/vscode-agent-kanban
I’m doing a fair amount of work on mobile, and prompting remote agents. I would love someone to build an OSS cross-platform kanban. It’d probably be complex to add triggers of workflows both locally and remotely though.
https://github.com/LachyFS/kanban-markdown-vscode-extension
Highly structured pseudo agile practices like scrum, never mind SAfE, make even less sense now than they did before. Flat collegial teams for the win.
Name and dates can also be stored in the filename and file metadata.
I wish I could unread it.
Storing the plan and discussion as Markdown in Git is an interesting approach. It basically treats the agent’s reasoning as part of the project history, not just the final code.
Curious if others here are doing something similar to keep context across sessions.
Would actually be cool to have more local tools like that, that something like Claude Code can integrate with. Find a bug in the code of your own implementation? Comment it in the issue, or add a new thing to fix, then at the end of implementation do a small retro and maybe end up with a SHORT sentence to add to CLAUDE.md on what to look out for in the particular project, OR create a new work item to make some additional prebuild scripts or tests.