Vibe Kanban (YC S21) | Rust + TypeScript | Open Source | London, UK (onsite) | Full-time | £80–120k + 0.5%

We're building the platform for engineers who spend most of their time planning and reviewing code written by AI. We’re hiring for two senior roles:

Frontend (TypeScript, React): https://jobs.polymer.co/vibe-kanban/36855?source=hn

Backend (Rust): https://jobs.polymer.co/vibe-kanban/36873?source=hn

The project is open source — check it out here: https://github.com/BloopAI/vibe-kanban

Are you sure you're using vibe-kanban? The project spins up a worktree for each task attempt specifically to solve this problem.

I would say conservatively that 80% of Vibe Kanban has been built by Amp

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

I concur :)

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

Interesting, hadn't heard of that. Would better GitLab support be useful in Vibe Kanban?

Yes, being able to use Gitlab as a provider would mean that we would jump on the tool, being Gitlab-based. :)

Very much a bet that things are going to get much much better very quickly

Yes I generally cherry pick the easier 50% of my backlog and work on those with Vibe Kanban, and the other 50% is still manual or happens with coding agent but with a human-in-the-loop.

This is a bet that coding agents will continue to get better, and this feels like the right time to try and figure out the interface.

I could see there being a long term free offering that doesn't cost us compute or tokens, and probably some other offerings that actually do use resources and would make sense to build a business around.

But that's not a today problem, we just want to absorb feedback and iterate until we build the ultimate tool for working with these coding agents.

Kanban seems like a good starting place, but I broadly agree that the interface for human<>agent collaboration will need to be different from the default interface we have today with legacy PM tools.

Things move across the board so quickly when AI is doing the work that ~50% of the columns seem pretty redundant.

It can open GitHub PRs from the interface and there's tons more info we want to pull in like the result of CI checks

Then you should have gone with a GitHub App instead of an Oauth App. The difference is that a GitHub App allows granularity of selection.