Vi Project Management
Project management that updates from your IDE
8 followers
Project management that updates from your IDE
8 followers
Vi Project Manager is a Git-aware project management tool for software teams. It helps developers complete tasks directly from their IDE, while the project board updates automatically. With Commit & Close, developers can commit, push, close a task, and move the workflow forward in one flow — reducing context switching and keeping project progress connected to real code changes.
The Commit & Close flow is genuinely useful, finally tying my branch updates to the board without jumping between terminal and browser. Would love to see how it handles merge conflicts mid-task.
@kyesilselv46136
Thanks — that’s exactly the workflow Vi is trying to improve: keeping the developer in the IDE while the board stays in sync with the real work.
For merge conflicts, Vi should not try to hide or magically resolve them. The source of truth is still Git and the developer’s IDE.
If a conflict happens mid-task, the right behavior is to keep the task active, show that the Git action needs attention, and let the developer resolve the conflict in their normal IDE/Git flow before the task is closed or moved forward.
So Commit & Close is meant to streamline the happy path, but not bypass Git’s safety mechanisms. Conflict handling is definitely an area I want to make very clear and developer-friendly.
Have you considered adding inline code snippet previews or diff summaries right on the task cards? Would be a huge help to see at a glance what changes actually shipped without needing to jump into Git or the IDE every time we review the board.
@oktay371908
Yes — that’s a great idea.
One important design principle for Vi is that it does not inspect or store a team’s source code by default. The focus right now is on connecting the IDE, Git actions, task completion, and board updates in one flow.
That said, I really like the idea of showing more context on task cards — especially a short “what changed” summary based on commits, files changed, or metadata, without exposing the actual source code unless a team explicitly enables that.
The key would be to keep it useful, not noisy, and give teams full control over how much code/context appears on the board.
Thanks for bringing this up — this is exactly the kind of feedback I was hoping to get.
One thing I’m especially trying to validate with this launch:
Do software teams actually want project boards to be updated from real development actions — commits, pushes, task completion — instead of relying on manual updates?
Vi is built around that idea: developers stay in the IDE, while the board stays connected to the real work.
I’d love to hear from developers and team leads: where does your current project board usually fall behind reality?