Solo Dev AI agent mode

[yassink]

The new workspace / project / team collaboration model is really confusing and adds a bunch of overhead I don’t need. I’m not collaborating with anyone. I don’t have a team. I just want a lightweight flow:

Create tasks → move them forward → hand off to OpenCode or whatever AI code agent.

That’s it.

Before the update, the Kanban was perfect for this: it was simple, fast, and everything worked smoothly. Now it feels like the board is designed primarily as a human or team Kanban tool, like Jira or Asana, and the extra structure gets in the way for solo AI code usage.

For me, the "Vibe-Kanban" board is not for humans collaborating—it’s effectively a control surface for the coding agent. I want to move tasks across stages to drive the agent workflow, not manage a workspace hierarchy.

If the product direction is “team Kanban,” that’s fine—but I’d strongly suggest a Solo Mode / Minimal Mode:

• no teams or cloud
• no collaboration setup
• no workspace/project complexity
• just a board + create tasks + agent handoff

If there’s a way to disable all the collaboration/workspace layers right now, I’d love to know how—because the previous flow matched my use case exactly.

[2001zhaozhao]

This a thousand times.

The new team-oriented flow is really annoying for solo use, which is especially frustrating since

• A lot of the ideas in the new version are actually quite solid
• It's literally against their interests to make solo usage difficult (it hampers adoption and make them have to pay for cloud capacity to individual users who they don't earn money from)

I do think it can be fixed to still allow solo usage while benefiting from some of the new features intended for teams.

• It's really helpful that each agent workspace can now be given multiple repositories and the board is shared between multiple repositories in a project. But one has to manually assign an agent in a separate GUI and manually assign repositories to start a task. It should be possible to create an agent with one-click, without having to leave the issue creation menu. You should be able to assign repositories to the agent in some easy fashion; for example it could be based on the issue tags, with each tag added causing one or more repositories to be automatically added to the issue.
• The cloud server is currently a PITA to self-host. It should honestly be one command execution to run both the server and the "client" (which is still a web server lol) locally, with the server running in single-user mode or username-password mode, without any login or 2FA setup required. (The team does seem to already be planning to make self-host easier, but IMO it should have been there on day 1). I get that the intent is to monetize from team usage, but you should still allow local usage of the whole stack and if devs like it, they'll recommend it to their companies anyway.
• Integrate the workspace feature into the kanban better. For example automatically moving the issue to done after merge - if not for team issues then at least create the concept of a personal issue where the AI determines the issue status on the personal board, if not automatically through MCP then at least moving to done when the human clicks merge. I can't believe this is not in. The team needs to understand that the point of VibeKanban is to make each developer act as the team leader of AI agents, and not be a generic kanban tool.
• Fix some new annoying UI aspects that add friction. For example there is an annoying "Confirm" screen when you merge a branch that you can't skip with keyboard (tab/space/enter etc. don't work) and require you to move your mouse from the right side of the screen to the middle to click it. Literally the king of crappy UX design right here. Make it skippable with enter key, move it closer to where the merge button is on the screen, and add a settings toggle to disable it completely. Related- why is the Merge button only accessible when you full-screen the workspace? It should be possible to complete small tasks without ever leaving the kanban page.
• Another example of annoying UI: why is it so damn difficult to delete/cancel an issue? Give us a space on the page that we can drag into to delete/cancel the issue. Or add a DEL key shortcut with a confirmation screen that has a keyboard shortcut. So we click an issue, hit DELETE then hit enter and boom it's cancelled.

Basically it boils down to simplifying the new flow and project setup so that solo developers can quickly fly through the UI while the advanced features remain there for teams that need it.