Vi Project Manager for Visual Studio

Your tasks, your timer, and your commits — in the IDE, not in a browser tab.

Vi Project Manager brings your Vi work queue directly into Visual Studio. Pick up a task, start coding, and let the extension handle the bookkeeping: the timer starts when you do, and finishing a task commits and pushes your work with the task id already in the message.

Commit & Close

This is the part you will notice on day one. When you mark a task Done:

Your changes are staged and committed as [#123] Fix payment rounding.
The commit is pushed.
The task is moved on in its workflow, and the timer stops.

If nothing was staged, the extension asks before closing the task with no changes attached. If a merge is still unresolved, it refuses to close the task at all — closing cannot be undone, and a half-finished merge is not something to discover afterwards.

Commits are also linked back to the task in Vi, so a task's history shows what actually shipped. Only commit metadata is sent — never your source code.

Your task list, in a tool window

View → Vi Project Manager → Vi: Open Tasks

Only your tasks. Pick a project and see what is assigned to you, grouped so subtasks always sit under their parent, sorted by what you are working on right now.
Search as you type by #id or title. It filters the list you already have — no waiting.
At-a-glance markers on every row: priority colour, 📎 attachments, subtask progress, and a red flag with the reason when a task was sent back to you.
Right there actions from the row menu: In Progress, Queued, Blocked, Done, Move to Next Step, Reject / Send Back with a note, Stop Timer, Open in Browser.
Task detail without leaving the IDE: description, comments (and add your own), attachments with download links, and subtasks you can add and tick off.

A timer that runs itself

Set a task to In Progress and the timer starts. Switch tasks, pause, or finish, and it stops. The elapsed time shows in the panel while you work, and it is the same timer the web app sees — no double entry, no forgotten stopwatch.

Shelve and restore

Moving a task from In Progress to Queued or Blocked offers to stash its working-tree changes, and picking the task back up offers to restore them. Your half-finished work stays with the task it belongs to instead of leaking into the next commit.

Subtasks that close cleanly

Closing a subtask commits your work but does not push — the push belongs to the real task. When you close the last open subtask, the extension asks whether to finish the parent too, and if you say yes it closes it and pushes everything at once.

Team chat

View → Vi Project Manager → Vi: Open Chat

Direct messages and group rooms with unread counts, so a quick "is this ready to merge?" does not cost you a context switch.

Getting started

Install the extension and restart Visual Studio.
Tools → Options → Vi Project Manager → General — enter your organization's tenant slug (the acme in acme.useviapp.com).
View → Vi Project Manager → Vi: Login — sign in with your Vi email and password.

Your access token is stored in the Windows Credential Manager, not in a settings file.

Requirements

Visual Studio 2022 or 2026 (17.x – 18.x), amd64 or arm64
.NET Framework 4.7.2 or later
A Vi account — there is a free plan, so you can try this without paying for anything
Git, for the commit features (a repository open in the current solution)

Good to know

The extension connects to useviapp.com only; self-hosted Vi servers are not supported.
The task panel shows tasks assigned to you in the selected project. To search across the whole organization — including other people's tasks, comments and activity history — use the search in the Vi web app.
Vi plugins are also available for VS Code, RAD Studio (Delphi) and Lazarus, so a mixed team can stay on the same board.

Vi Project Manager

Vi