Top
Best
New

Posted by gbro3n 10 hours ago

Show HN: VS Code Agent Kanban: Task Management for the AI-Assisted Developer(www.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

80 points | 37 commentspage 2
ssgodderidge 7 hours ago|
Great to see more products in this space! Definitely going to try this out on desktop.

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.

gbro3n 7 hours ago|
Maybe it will go that way eventually. I haven't got into being able to hand off to agents in the cloud yet, I think as good as LLMs are getting, for complex / professional work the agents still need a lot of steering. I just have to be in the editor with the agent!
bryanhogan 3 hours ago||
Sorry for the slightly unrelated comment, but the amount of AI written slop comments here is so high. Was this caused by mentioning "AI" in the title?
Sakthimm 2 hours ago|
I think OpenClaw is the reason we are getting so much AI slop these days. The comments here with "key insights" are coincidentally < 1 month old. It seems for some reason, OpenClaw/NanoClaw loves Show HN posts.
wek 7 hours ago||
This is interesting. We've seen markdown as the app. This is markdown as the database for your tasks.
empath75 6 hours ago||
I had claude build me something similar for my own autonomous agent system, because I was irritated at how much friction Jira has. I suspect a lot of people will do this.
xxwink 5 hours ago||
As a project manager returning to coding after 20 years — this is directly relevant to my experience. AI can genuinely augment both productivity and creativity, but it needs strong process and constraints to do it well. What separates throwaway AI code from something maintainable is product vision and tooling that keeps the AI focused. This looks like a step in that direction.
gbro3n 5 hours ago|
Having used a less formalised version of the process (manually managing the agent files but having the user / agent conversation structure the same), I've been getting some really good results out of the agent on some long running complex tasks. I'm seeing so many people talking about leaving agents running and completing projects end to end without any intervention, but my experience so far is that decent software still needs architecture guidance and a human sense of 'taste'.
varispeed 5 hours ago||
Every time I see this phrase: "Why This Matters"

I wish I could unread it.

gbro3n 3 hours ago|
Harsh but fair!
termwatch 7 hours ago||
interesting feature!
naomi_kynes 7 hours ago||
[dead]
guerython 6 hours ago||
[flagged]
gbro3n 6 hours ago|
Agreed. Also multiple humans. One task per person works great (no Git conflicts). I'll think about this more. I'm thinking that having the agent work through an MCP server might be a means of mitigating the issue. I'd rather keep the sync process in Git if I can.
hkonte 4 hours ago|
[dead]
gbro3n 4 hours ago|
Structure certainly helps, and that's what the markdown format here does. How do you measure the effect of the structure?