Would you prefer to work on your Renku project from the comfort of your local VSCode rather than in the browser? This how-to guide shows you how to do exactly that!

<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" />

VSCode tunnels are supported in the following Renku session environments:

In RenkuLab:

  1. Launch a Renku session that uses one of the supported environments listed above.
  2. Open a terminal inside the session.
  3. Run start_tunnel and follow the instructions:
    1. Log in to VSCode with either your Microsoft account or GitHub account
    2. Open the displayed link and enter the device code
    3. When it shows you another URL to open, you are done. Continue to the next steps.

Then, in a VSCode window on your local machine:

  1. Install the “Remote - Tunnels” VSCode Extension if you don’t already have it.

    image.png

  2. In the very bottom left of the window, click the Open a Remote Window button

    The ‘Open a Remote Window’ button

    The ‘Open a Remote Window’ button

  3. Pick Connect to Tunnel...

  4. If you’re not signed in, you’ll be asked to sign in. Sign into the same account you did when running the start_tunnel script

  5. You should now see a list of available tunnels on your account, and one of them should be a renku-... tunnel. Select it!

    image.png

    <aside> <img src="/icons/light-bulb_yellow.svg" alt="/icons/light-bulb_yellow.svg" width="40px" />

    Tip: Do you have more than one Renku session tunnel? You can find the name of the tunnel for each session by looking at beginning of the logs of start_tunnel. The line looks like this:

    [2025-09-01 12:06:23] info Creating tunnel with the name: renku-1189b3f2321d0b
    

    </aside>

  6. If no files show up at first, click the Open… shortcut and enter /home/renku/work/

    image.png

  7. You should now see the same files you see in your RenkuLab session, and you can do work exactly like you are in a RenkuLab session!

Done with your session?

  1. Close the VSCode window
  2. Back in the browser, pause or shut down your Renku session