Vi — Project Management for VS Code

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

Vi is Git-aware project management for software teams — tasks, custom workflows, approvals, time tracking and project boards. This extension puts that work queue inside VS Code and adds Commit & Close: marking a task Done commits the files you pick with the task id, pushes them, and moves the task to the next step of its workflow — in one action.

Commit & Close

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

1. You tick the files that belong to the task. Files you already staged are ticked for you (everything is, if nothing is staged); the rest stays in your working tree.
2. Vi checks that the task may move on — approvals, open subtasks, dependencies — before anything is committed.
3. The files are committed as [#123] Fix payment rounding and pushed (no remote configured: committed only).
4. Only then does the task finish your step and move to the next one in its workflow, and the timer stops.

If the push fails, the task stays on its step as Awaiting push and choosing Done again retries — so a task never reaches the next person (QA, say) without its code on the remote. If there are no changes at all, the extension asks before finishing with nothing committed. If a merge is still unresolved, it refuses outright — a half-finished merge is not something to discover afterwards.

Commits are 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.

Git work goes through VS Code's own built-in Git extension, so it uses the repository and credentials you already have set up.

Close a task from your AI assistant

Connected to Vi through MCP, an AI assistant (Claude Code, Cursor, …) can ask you to finish a task. Nothing happens on its own: a window opens in the VS Code that has the task's project (the one with the .vi link), saying who asks and for which task. If you approve, you pick the files and the very same Commit & Close runs; if you decline, nothing is committed. Only your own main tasks, only in your own VS Code, and the request expires after three minutes.

Your task list, in the sidebar

• 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, attachments, subtask progress, and a flag with the reason when a task was sent back to you — kept until the task moves forward again, so it is still there while you fix it.
• Actions where you are: In Progress, Queued, Blocked, Done (+ Commit), Reject / Send Back with a note, Open in Browser.
• Task detail without leaving the editor: description, comments (and add your own), attachments, and subtasks you can add and tick off.
• Open the panel as a full editor tab when the sidebar gets cramped.

One project per folder

Pick the Vi project once and it is remembered in a small .vi file in the workspace folder; from then on the panel opens straight on it, without asking. Commit the file and the whole team opens on the same project. Change next to the project name links the folder to another one.

Notifications, as they happen

Assigned a task, a task moved to you, a rejection, a new comment — they appear as VS Code notifications the moment they happen, with Open Task to jump to it, and the task list refreshes itself. A chat message for a conversation you don't have open shows up the same way. This works whether or not the Vi views are open.

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 is live in the panel, and it is the same timer the web app sees — no double entry, no forgotten stopwatch.

Start clean, shelve and restore

Starting a task while the working tree already has changes, the extension asks what to do with them first — keep them, commit them, or stash them — so another task's edits don't end up in this task's commit. Moving a task from In Progress to Queued or Blocked offers to stash its changes, and picking the task back up offers to restore them. Half-finished work stays with the task it belongs to.

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, in real time

Direct messages and group rooms with unread badges, delivered over a live connection rather than polling — so a quick "is this ready to merge?" does not cost you a context switch.

Getting started

1. Install the extension.
2. Open the Vi icon in the Activity Bar (or run Vi: Login).
3. Sign in with your organization's tenant slug (the acme in acme.useviapp.com), your Vi email and your password.

There is nothing to configure: the tenant is the one you sign in to. Work for several organizations? Each keeps its own login, and a project linked to another organization (its .vi file) switches to it — with the sign-in form filled in except for the password. Your access tokens are stored in VS Code's SecretStorage, not in a settings file.

Commands

Requirements

• VS Code 1.85 or later
• A Vi account — there is a free plan, so you can try this without paying for anything
• Git and an open repository, for the commit features

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 Visual Studio, RAD Studio (Delphi) and Lazarus, so a mixed team can stay on the same board.

Links

• useviapp.com — what Vi is
• Commit & Close, explained
• Pricing
• Contact us