Juni Pro AI uses local Docker context instead of configured Remote Docker over SSH

Junie AI does not respect the Docker context (SSH Remote) configured in JetBrains IDEs. When analyzing errors or environment state, Junie attempts to query the local Docker daemon instead of the remote one defined in the Run/Debug configuration. Furthermore, if forced to look at the remote host, it fails to locate source code because it expects them to be on the remote server, ignoring the local-to-remote deployment structure.

To Reproduce

Set up a Docker server in PyCharm via SSH (e.g., user@remote-host).

Run a docker-compose configuration using this remote server (Source code is Local, Docker containers are Remote).

Trigger an error within the container or code.

Ask Junie to diagnose the error or explain the container state.

Expected behavior

Junie should identify that the active Docker configuration uses a Remote SSH Server and execute its diagnostic queries (docker logs, docker ps, etc.) on that remote host.

Junie should map the remote container logs/errors back to the local source files currently open in the IDE.

Actual behavior

Scenario A: Junie queries the local machine's Docker engine. Since the containers only exist on the remote host, Junie reports that no containers are running or provides irrelevant data.

Scenario B: If I manually instruct Junie to use the remote host, it looks for the source code at the remote path (e.g., /home/tomek/GX1_Projects/...). However, since this is a local development setup, the source code resides on the local machine, and the remote only has the runtime environment.

Environment:

IDE: PyCharm 2026.1 (Professional Edition)

Plugin: Junie Pro

Docker Setup: Remote via SSH

OS: Linux (Local) / Linux (Remote)

Additional context
The IDE itself handles this setup perfectly—running docker compose up works as expected, deploying from local to remote. The issue is strictly isolated to the Junie plugin's inability to switch its context to the Remote Docker Engine while maintaining the Local file context.