0

I'm running VS Code on Windows:

Version: 1.104.0 (user setup)
Commit: f220831ea2d946c0dcb0f3eaa480eb435a2c1260
Date: 2025-09-10T06:46:18.035Z
Electron: 37.3.1
ElectronBuildId: 12342881
Chromium: 138.0.7204.235
Node.js: 22.18.0
V8: 13.8.258.31-electron.0
OS: Windows_NT x64 10.0.22631

It's connected to a remote host on linux.

I've installed Perforce for VS Code [(2020 Fork) Perforce integration with VS Code's SCM features]

Identifier
mjcrouch.perforce
Version
4.16.2
Last Updated
2025-09-11, 14:54:26

VS Code opens a source code with Perforce SCM. However, extension cannot identify the perforce client in the current directory. Current directory contains correct .p4config.

Found workspace using root directory
  * VS Code workspace root directory :
    Client name: <client name>
    Client root: <client root>
    User name: <user name>
    Server address: <p4port>
!!  Folder IS NOT in client root - IGNORING THIS CLIENT

Folder is a correct p4 client root. I am able to run all p4 clis. However, the extension is not able to identify the client root.

I have tried using perforce.activationMode = Always.

Improve this question
4
  • 2
    I expect that <client name> and/or <client root> is incorrect and/or that <client root> doesn't match whatever folder you opened in VSCode. If I knew which piece of the configuration was wrong I could probably advise on how to fix it, but all of those details are absent from the question. Commented Sep 11 at 23:45
  • Seconding what Samwise said. If you can give us the directory you opened as well as the details of the workspace like Client Root we could probably help more. Commented Sep 11 at 23:58
  • You might want to try going to that folder at the CLI and running p4 info and verifying that the client name matches what VSCode is reporting -- then run a command on the files in that folder (the ... relative path, e.g.p4 files ...), and make sure that you get valid results instead of not in client view. My guess is that one or both of those commands will reveal a discrepancy. Commented Sep 12 at 17:08
  • I have run p4 info and p4 files on the machines and they are correctly pointing to the client and depot . Basically, when I use CLI everything is working as expected. Commented Sep 12 at 22:28
Related questions
0
.vscode no longer in a workspace
1
VS Code keeps overwriting eslint setting
8
Perforce P4CONFIG not being set?
Load 3 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.