posit-dev / posit-dev/positron

Document what scripts, etc get run for remote SSH sessions

Open
#8,638 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area: remote host documentation
Dominant language
TypeScript
Stars
4.3k
Forks
184
Avg merge
1d 9h
Merged PRs (30d)
195

Description

System details:

Mac, Sequoia 15.5, sshing into a Debian GNU/Linux 11 (bullseye) x86_64

Positron and OS details:

Positron Version: 2025.07.0 build 204
Code - OSS Version: 1.100.3
Commit: 03ae7a5393c776bb24c23d2aa6a6bfbba90cbc5e
Date: 2025-06-30T16:29:03.492Z (3 wks ago)
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Interpreter details:

Python 3.9.2 (old, I know0

Describe the issue:

RemoteHost ssh does not run the .profile file when it connects to remote machine.

On the remote machine, there is a .profile file which is just the line

sudo su - new_user

when I run the command in the terminal

ssh -i ~/.ssh/... username@ip_address

then the file correctly runs .profile and I am the correct user at the repl.

When I do Remote-ssh: Connect to host in VS Code, it likewise works.

However when I do the same on Positron

When I do Remote-ssh: Connect to host and enter in my command

ssh -i ~/.ssh/... username@ip_address

then I am the original username, not the new one that the .profile switches to.

I think the cause might have something to do with the R version on my remote machine. For whatever reason, the R version on my remote machine is super old, R 4.0.4, a version unsupported by Positron.

My guess is that there is an error when trying to connect to an R instance, and this error happens before running .profile. Then it skips that command?

I am not sure how to get a more up-to-date version of R. when I use rig I get a 403 error... I guess I should talk to my system administrator.

Steps to reproduce the issue:

  1. Install remote connection extension
  2. Run the "setup remote connection" command
  3. Input the ssh command

Expected or desired behavior:

Same behavior as VS Code

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the “setup remote connection” command and the reported SSH command, then compare Positron’s behavior with VS Code Remote-SSH. Document which scripts run during remote SSH sessions, including whether .profile is sourced, and verify the explanation against the reported Debian environment.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.