TFVC for IntelliJ IDEA

Keep the TFS flow.Lose the legacy friction.

Browse TFVC history, inspect diffs, and update a single file without leaving IntelliJ IDEA. TFS Remake brings everyday version control closer to your code, with the familiar TFS workflow.

Download plugin View on GitHub How to set up

TFVC
REST
IntelliJ IDEA 2022.3 target
Java 11 target

Your existing workflow

Your code stays in TFVC.
You stay in IntelliJ.

Built on the JetBrains TFS plugin

Keep the tools you know.

Keep working with Local Changes, Repository, Show History, and Annotate. Your existing TFVC repository remains the source of truth.

Modern authentication

Choose how you sign in.

Use a personal access token for REST operations, or Microsoft Entra sign-in with MFA for Azure DevOps Services.

Credential storage

Credentials, kept separate.

Saved PATs and passwords use IntelliJ Password Safe. If secure storage is unavailable, saving fails rather than writing secrets into the connection settings.

Everyday version control

See the change.
Choose the next step.

Follow a changeset down to the code. Update what you need. Bring a rollback into Local Changes for review before check-in.

Browse & inspect

From changeset to code.

Repository

Find the change that matters.

Repository loads recent changesets on open. Scroll for older history and select a changeset to see the files it changed.

Show History

See what changed in the file.

Select a revision to see its changed files, then choose one to open the inline diff preview.

Stay current

A project update.
Or just one file.

Update Project

Skip unnecessary downloads.

Where supported, Update Project uses known changes and local state to avoid re-downloading current files.

Update File from TFS

Bring one mapped file up to date.

Target a single file. Repository history and file update notifications take the place of IntelliJ's standard Incoming view.

Act deliberately

A way back.
A clearer record.

Rollback

Review locally. Check in deliberately.

Apply a supported rollback locally and review Local Changes before check-in. Or explicitly create a server rollback changeset.

Changeset comments

Correct the explanation.

Edit a changeset comment directly from its menu in IntelliJ, without switching to a separate client.

Setup

From ZIP to working copy.

Install the plugin, connect your server, and map an existing TFVC workspace to your project in IntelliJ.

Step 1 · Install & sign in

Install the ZIP.
Choose your sign-in.

In IntelliJ Settings → Plugins, open the settings menu and choose Install Plugin from Disk... Select the downloaded ZIP and restart if prompted.

Personal access token

Sign in with a PAT.

Create a PAT in Azure DevOps with only the permissions required for the operations you use.
In the server dialog, choose Basic/alternate-compatible. Enter your username and PAT; enable credential storage to save it.

SSO / MFA

Microsoft Entra.

For Azure DevOps Services, choose Microsoft Entra SSO/MFA and provide your organization's tenant and client ID.
Choose Sign in with Microsoft... and complete the browser flow. Confirm the signed-in account before saving. No PAT is needed for this path.

Step 2 · Server

Connect your server.

Open TFS → Edit Configuration... → Add server. Enter your Azure DevOps organization or TFS collection URI and configure sign-in.
Saving stores the connection. It does not create a TFVC workspace, check out files, or run an update.

Step 2 Add the server row dialog with server URI, authentication choice, credential fields, and proxy URI — Add TFS Server — connection, authentication, credential storage, and proxy settings.

Step 3 · Workspace

Connect the two sides.

Select the saved server and choose Add local mapping...
Use the existing TFVC workspace name, its server path beginning with $/, and the matching absolute local folder.
Keep the mapping active. This links the paths in your project; it does not modify the server workspace.

Step 3 explicit mapping dialog with server URI, workspace name, TFVC server path, local path, and active mapping checkbox — Edit REST Check-In Mapping — one explicit TFVC-to-local boundary.

Step 4 · Verify REST

Test the connection.

In Edit Configuration..., select the server and run Test REST connection.
401: check sign-in. 403: check the account's permissions.

Step 5 · IntelliJ

Tell IntelliJ where to work.

Open Settings → Version Control → Directory Mappings. Add the same local root and choose TFS.
Both mappings are needed: the REST mapping connects the paths; the IDE mapping marks the folder as version-controlled.

TFS Remake

Keep your focus on the code.

Your TFVC repository. Your familiar IDE. A more direct path through everyday version control.

Download plugin Review setup GitHub