Remote SSH Python Interpreter - Multiple Regressions Since 2025.3+

IntelliJ IDEA Version: 2026.1.2 (also reproducible on 2025.3+) OS: macOS (MacBook Pro) Python Plugin: Bundled (latest)

Setup

I use a MacBook Pro (local) and a remote Linux instance for development. My workspace folder is kept in bidirectional sync between the two machines using an external sync tool (not managed by IntelliJ). Build tools are only available on the remote instance.

During builds on the remote instance, a Python virtual environment is created at workspace/.venv/ containing the interpreter and all dependencies in site-packages. I configure a remote SSH Python interpreter in IntelliJ pointing to this venv to get code completion, type hints, and navigation.

My goal: Code intelligence (completion, type hints, go-to-definition) using the remote interpreter's packages. I do NOT need IntelliJ to manage file deployment/sync.

How I configure the interpreter: File → Project Structure → Platform Settings → SDK → + Add Python SDK from disk → SSH → Existing → Environment: Existing | Type: Python | Python Path: workspace/.venv/bin/python → Target Specific Properties → untick "Automatically upload project files on the server" → Create

Issue 1: Packages tab permanently shows "Nothing to show"

Expected (worked in versions before 2025.3): After creating the SSH Python SDK, the Packages tab (Project Structure → SDKs → [SDK] → Packages) would display all installed packages from the remote site-packages.

Actual (2025.3+): The Packages tab permanently shows "Nothing to show." Helpers upload and dependency caching appear to complete successfully, but the package list never populates.

Issue 2: Renaming SDK breaks Module Dependencies

Steps to reproduce:

  1. Create a new SSH Python SDK (as described above)
  2. Rename the SDK immediately after creation
  3. Go to Project Settings → Project → select the renamed SDK
  4. Go to Project Settings → Modules → Dependencies

Expected: Module dependencies should follow the rename.

Actual: The Module Dependencies still reference the old (pre-rename) SDK name, which no longer exists. I have to manually go to Modules → Dependencies → Module SDK dropdown and reselect the renamed SDK every time. This was not an issue in versions before 2025.3.

Issue 3: Dependencies never refresh/rescan

Expected (worked in versions before 2025.3): When new packages were installed in the remote venv (e.g., after a build pulls new dependencies), IntelliJ would eventually detect and index them — at minimum after an IDE restart.

Actual (2025.3+): The IDE never rechecks the remote interpreter's packages. Even after closing and reopening IntelliJ, newly installed remote packages are not picked up. There seems to be no automatic or periodic rescan. A manual way to trigger this would also be acceptable, but I haven't found a reliable one.

Issue 4: "Introspecting SSH server" step is slow/hangs

Observed: When creating a new SSH interpreter, there is now an "Introspecting SSH server" step that did not exist in earlier versions. It sometimes hangs or takes a very long time. This step does not appear to be useful for my use case and I cannot find a way to disable it.

Additional Observation

In previous versions, creating an SSH interpreter would also create a Deployment configuration by default. This no longer happens in 2025.3+. I don't believe I need a deployment (since I manage sync externally), but noting it in case it's related to the package detection issues above.

Questions for the Community

  1. Is anyone else experiencing the "Nothing to show" issue with remote SSH Python interpreters on 2025.3+?
  2. Is there a reliable way to force IntelliJ to rescan/refresh remote packages?
  3. Is the SDK rename → module dependency breakage a known bug?
  4. Can "Introspecting SSH server" be disabled or skipped?

Any suggestions or workarounds would be greatly appreciated. This workflow was working perfectly in versions prior to 2025.3.

 

 

0

In older versions, an SSH interpreter was treated almost like a local SDK with a remote execution path, implicitly relying on hidden SFTP deployment mappings. In recent releases (2025.3 through 2026.1), JetBrains shifted toward a decoupled architecture that heavily relies on target introspection and explicit internal deployment configurations to build the package skeleton cache. Because you explicitly unlinked deployment management ("Automatically upload project files on the server"), the IDE’s background system is breaking on several fronts. 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

paygonline login

0

What are the options that I have to make this work? Even if I enable “Automatically upload project files on the server”, it would not help me because when I build, there are lots of new files created/modified which needs to be synced back to the laptop.

 

For now, if I just enable “Automatically upload project files on the server”, will it work for me?

0

请先登录再写评论。