Live data from Hacker News

Show HN: Vibe Kanban – Kanban board to manage your AI coding agents

github.com

91–100 of 137 posts

Re: Show HN: Vibe Kanban – Kanban board to manage your AI coding agents

#91

Earlier quoted context omitted.

> AI coding agents are increasingly writing the world's code and human engineers now spend the majority of their time planning, reviewing, and orchestrating tasks. This tactic is called "assuming the sale". ie, Make a statement as-if it is already true, and put the burden on the reader to negate it. Majority of us are too scared of what others think, and go-along by default. It is related to the FOMO tactic in that i…

I'll add - often not adding the last part is even MORE powerful: "and everyone is now using agents to increase their productivity..."

[deleted]

Re: Show HN: Vibe Kanban – Kanban board to manage your AI coding agents

#92
post #87

Earlier quoted context omitted.

That's fair feedback, I have a PR with a very clear opt-in here https://github.com/BloopAI/vibe-kanban/pull/146 I will leave this open for comments for the next hour and then merge.

Nice, I vote for merging it :). It really doesn't hurt to be honest about this and ask up-front. This is clear enough and benign enough that I'd actually be happy to opt-in.

Merged and building, thanks for bearing with us

Re: Show HN: Vibe Kanban – Kanban board to manage your AI coding agents

#93

Earlier quoted context omitted.

fork, task claude to remove all github dependence, build.

Use a telemetry backed tool to remove telemetry from another telemetry backed tool?

There's telemetry you consent to, and telemetry you don't. Just because I'm fine with a tool like Claude Code collecting some telemetry, doesn't mean I'm fine with a different party collecting telemetry - and the two products being used together doesn't change it. It's not naive, it's simply my right.

Re: Show HN: Vibe Kanban – Kanban board to manage your AI coding agents

#94
post #87

Earlier quoted context omitted.

That's fair feedback, I have a PR with a very clear opt-in here https://github.com/BloopAI/vibe-kanban/pull/146 I will leave this open for comments for the next hour and then merge.

Nice, I vote for merging it :). It really doesn't hurt to be honest about this and ask up-front. This is clear enough and benign enough that I'd actually be happy to opt-in.

I concur :)

Re: Show HN: Vibe Kanban – Kanban board to manage your AI coding agents

#95

The permissions this asks for feel kinda insane to me. Why does a kanban board need to see the code or my deploy keys among other things?

Because it's not "a kanban board"? It's a coding agent orchestrator that's made in the shape of a Kanban board.

You might be right that this app asks for excessively broad privileges, but your case would be much stronger if it wasn't backed by an absurdly disingenuous argument.

Re: Show HN: Vibe Kanban – Kanban board to manage your AI coding agents

#96
post #77

Earlier quoted context omitted.

fork, task claude to remove all github dependence, build.

I did this locally to try it out :) Also stubbed out the telemetry and added jj support. "Personalizing" software like this is definitely one of LLMs superpowers. I'm not particularly inclined to publish it because I don't want to associate myself with a project harvesting emails like this.

> and added jj support

Please do the same for Aider :-)

https://github.com/Aider-AI/aider/issues/4250

Re: Show HN: Vibe Kanban – Kanban board to manage your AI coding agents

#97
post #96
post #77

Earlier quoted context omitted.

I did this locally to try it out :) Also stubbed out the telemetry and added jj support. "Personalizing" software like this is definitely one of LLMs superpowers. I'm not particularly inclined to publish it because I don't want to associate myself with a project harvesting emails like this.

> and added jj support Please do the same for Aider :-) https://github.com/Aider-AI/aider/issues/4250

Be the change you want to see! This is pretty close to a best case task for these models because it's a relatively direct "translation" of existing code.

There's a big difference between "something actually ready for use" and "claude hacked sometime together with bubblegum and ducttape that works on my system" though - doing it properly will probably take a bit of work.

Re: Show HN: Vibe Kanban – Kanban board to manage your AI coding agents

#98
post #87
post #51

Hmm, analytics appear to default to enabled: https://github.com/BloopAI/vibe-kanban/blob/609f9c4f9e989b59... It is harvesting email addresses and github usernames: https://github.com/BloopAI/vibe-kanban/blob/609f9c4f9e989b59... Then it seems to track every time you start/finish/merge/attempt a task, and every time you run a dev server. Including what executors you are using (I think this means "claude code" or the li…

That's fair feedback, I have a PR with a very clear opt-in here https://github.com/BloopAI/vibe-kanban/pull/146 I will leave this open for comments for the next hour and then merge.

Good on you for taking action on this kind of feedback!

Re: Show HN: Vibe Kanban – Kanban board to manage your AI coding agents

#99
So far, it’s relatively bug-free well-written code that I’ve forked to work behind the walls of a hedge fund, and it works, but the reality is that it doesn’t provide anything that some terminal windows and git worktrees can’t offer. Am I missing something?

You really need to add more features, because I struggle to find a compelling reason for advanced users to use it.

Re: Show HN: Vibe Kanban – Kanban board to manage your AI coding agents

#100

This is a launch by a YC company that converts enterprise cobol code into java. Maybe it's my fault, but i tried every single coding agent with a variety of similar tools and whenever i try to parallelize, they clash while editing files simultaneously, i lose mental context of what's going on, they rewrite tests etc. It's chaos. Thats fine if you are vibe coding an unimportant nextjs/vercel demo, but i'm really scept…

> Maybe it's my fault, but i tried every single coding agent with a variety of similar tools and whenever i try to parallelize, they clash while editing files simultaneously, i lose mental context of what's going on, they rewrite tests etc. Fwiw Claude suggests using different git workspaces for your agents. This would entirely solve the clashing, though they may still conflict and need normal git conflict resolves o…

This works in theory and somewhat in practice but it is not as clean as people make it seem, as someone who has spent tens of thousands on Opus tokens and worktrees - it’s just not that great. It works, but it’s just, ugh, boring, super tedious, etc. at the end of it all, you’re still sitting around waiting for Claude to merge conflicts.
Post reply on HN