<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Interactive-Job on Oxford RSE</title><link>/tags/interactive-job/</link><description>Recent content in Interactive-Job on Oxford RSE</description><generator>Hugo</generator><language>en-GB</language><copyright>Copyright (c) 2023 Oxford RSE</copyright><lastBuildDate>Wed, 17 Jun 2026 13:45:47 +0000</lastBuildDate><atom:link href="/tags/interactive-job/index.xml" rel="self" type="application/rss+xml"/><item><title>Connecting VS Code to a Cluster</title><link>/blog/connecting-vs-code-to-a-cluster/</link><pubDate>Wed, 17 Jun 2026 13:45:47 +0000</pubDate><guid>/blog/connecting-vs-code-to-a-cluster/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;If you use the ARC clusters at Oxford and want to use your local editor (such as Visual Studio Code) for editing and debugging code on the cluster, you’ll quickly find that you &lt;strong&gt;can’t&lt;/strong&gt; just connect to the login node and launch VS Code’s Remote-SSH as you might on a regular remote server. In this post I’ll explain &lt;strong&gt;why you can’t launch VS Code directly on the login node&lt;/strong&gt;, then walk you through the workflow: starting an interactive job, configuring SSH proxy-jump, and connecting VS Code to the interactive node. Note that while I&amp;rsquo;m talking about Oxford&amp;rsquo;s ARC cluster here, the general principles apply to working with VS Code on any remote cluster which has a low-compute resource login node.&lt;/p&gt;</description></item></channel></rss>