<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Dmitry Matveyev - Blog</title>
    <link>https://www.dmitrymatveyev.com/blog/</link>
    <atom:link href="https://www.dmitrymatveyev.com/blog/feed.xml" rel="self" type="application/rss+xml"/>
    <description>Notes on legacy modernization, AI-assisted development and building micro-startups.</description>
    <language>en</language>
    <lastBuildDate>Sun, 15 Nov 2026 09:00:00 GMT</lastBuildDate>
    <item>
      <title>isolde: a separate Linux desktop for every project</title>
      <link>https://www.dmitrymatveyev.com/blog/isolde/</link>
      <guid isPermaLink="true">https://www.dmitrymatveyev.com/blog/isolde/</guid>
      <pubDate>Sun, 15 Nov 2026 09:00:00 GMT</pubDate>
      <dc:creator>Dmitry Matveyev</dc:creator>
      <description>isolde gives each project directory its own Linux desktop in Docker, reachable over RDP: a real browser, a terminal and a separate home for Claude Code in every project.</description>
      <content:encoded><![CDATA[<p>I run Claude Code on most of my projects, and I wanted it to have its own computer for each one: a desktop with a real browser, a terminal, and a home directory that stays separate from everything else. isolde is the small tool I built for this. It gives each project directory its own Linux desktop in Docker, which you reach over RDP.</p>
<p>The idea of a development container isn&#39;t new. What isolde adds is a full desktop, so you can watch what Claude Code is doing in a browser, log in to web portals yourself, and step in when needed. I&#39;ve been using it daily, and this article walks through the basic setup and usage.</p>
<p>The source is on GitHub: <a href="https://github.com/dmitrymatveyev/isolde">github.com/dmitrymatveyev/isolde</a>.</p>
<h2 id="what-you-get"><a class="anchor" href="#what-you-get" aria-hidden="true" tabindex="-1">#</a>What you get</h2>
<p>When you run <code>isolde</code> in a project directory, it starts a container with:</p>
<ul>
<li><strong>Your project at <code>/workspace</code>:</strong> the directory you ran it from is mounted into the container, so changes appear on the host straight away.</li>
<li><strong>A home of its own:</strong> each project directory gets its own <code>/home/dev</code>, stored in a Docker volume. It keeps your settings, logins and history when the container stops or the image is rebuilt.</li>
<li><strong>A desktop over RDP:</strong> XFCE on Ubuntu 24.04, served by xrdp.</li>
<li><strong>Tools for working with Claude Code:</strong> Claude Code, the kitty terminal, tmux, Chromium and Playwright, plus common tools such as <code>git</code>, <code>gh</code>, <code>ripgrep</code> and <code>jq</code>.</li>
</ul>
<p>Two projects never share a home, so a login, a browser profile or a configuration change in one project doesn&#39;t reach the others.</p>
<h2 id="requirements"><a class="anchor" href="#requirements" aria-hidden="true" tabindex="-1">#</a>Requirements</h2>
<ul>
<li>Docker</li>
<li>An RDP client</li>
<li><code>bash</code> and <code>sha256sum</code> on the host</li>
</ul>
<p>So far I&#39;ve only tested isolde on my own Linux machine. Docker Desktop on macOS or Windows and ARM hosts haven&#39;t been tried yet.</p>
<h2 id="step-1-build-the-image"><a class="anchor" href="#step-1-build-the-image" aria-hidden="true" tabindex="-1">#</a>Step 1: Build the image</h2>
<p>Clone the repository and build the image from it:</p>
<pre><code class="language-bash">git clone https://github.com/dmitrymatveyev/isolde.git
cd isolde
docker build --build-arg HOST_UID=$(id -u) --build-arg HOST_GID=$(id -g) -t isolde .
</code></pre>
<p>The two build arguments give the container&#39;s <code>dev</code> user the same UID and GID as your host user. Files that Claude Code or you create in <code>/workspace</code> are then owned by you on the host, not by root.</p>
<p>The first build takes a while, because it installs the desktop, Node.js, Claude Code and Chromium.</p>
<h2 id="step-2-put-isolde-on-your-path"><a class="anchor" href="#step-2-put-isolde-on-your-path" aria-hidden="true" tabindex="-1">#</a>Step 2: Put <code>isolde</code> on your PATH</h2>
<p>Link the script into a directory on your <code>PATH</code>:</p>
<pre><code class="language-bash">ln -s &quot;$PWD/isolde&quot; ~/.local/bin/isolde
</code></pre>
<p>Use a symlink rather than a copy, because the script needs a file that sits next to it in the repository.</p>
<h2 id="step-3-start-a-desktop-for-a-project"><a class="anchor" href="#step-3-start-a-desktop-for-a-project" aria-hidden="true" tabindex="-1">#</a>Step 3: Start a desktop for a project</h2>
<p>Go to the project you want to work on, choose a password for the desktop, and run <code>isolde</code>:</p>
<pre><code class="language-bash">cd ~/projects/foo
export RDP_PASSWORD=&#39;choose-something&#39;
isolde
</code></pre>
<p>It prints the address to connect to:</p>
<pre><code>/home/you/projects/foo -&gt; RDP at 127.0.0.1:49153 (user: dev)
</code></pre>
<p>Docker picks a free port each time a container starts, so the port can change between starts. Running <code>isolde</code> again in the same directory prints the address of the running container without starting a new one.</p>
<h2 id="step-4-connect-over-rdp"><a class="anchor" href="#step-4-connect-over-rdp" aria-hidden="true" tabindex="-1">#</a>Step 4: Connect over RDP</h2>
<p>Open your RDP client and connect to the printed address:</p>
<ol>
<li>Enter the address, for example <code>127.0.0.1:49153</code>.</li>
<li>Log in as <code>dev</code> with your <code>RDP_PASSWORD</code>.</li>
<li>Choose the <code>Xorg</code> session if you&#39;re asked.</li>
<li>Accept the certificate warning. xrdp uses a self-signed certificate.</li>
</ol>
<p>You now have an XFCE desktop. Your project is at <code>/workspace</code>, and kitty and Chromium are set as the default terminal and browser. The port is bound to <code>127.0.0.1</code>, so only the host can reach it.</p>
<h2 id="step-5-run-claude-code"><a class="anchor" href="#step-5-run-claude-code" aria-hidden="true" tabindex="-1">#</a>Step 5: Run Claude Code</h2>
<p>Open a terminal on the desktop and start Claude Code:</p>
<pre><code class="language-bash">cd /workspace
claude
</code></pre>
<p>The first time, log in as usual. The login is stored in the project&#39;s home, so you only do this once per project directory.</p>
<p>Chromium is available from the applications menu or with the <code>chromium</code> command, and it runs with its sandbox turned on.</p>
<h2 id="step-6-open-a-shell-from-the-host"><a class="anchor" href="#step-6-open-a-shell-from-the-host" aria-hidden="true" tabindex="-1">#</a>Step 6: Open a shell from the host</h2>
<p>You don&#39;t need the desktop for terminal work. From the project directory on the host, run:</p>
<pre><code class="language-bash">isolde shell
</code></pre>
<p>This opens a shell in <code>/workspace</code> inside the same container, using your terminal&#39;s color settings. If the container isn&#39;t running, it&#39;s started first, so <code>RDP_PASSWORD</code> has to be set. Typing <code>exit</code> closes the shell and leaves the container running.</p>
<p>tmux is included and set up for Claude Code, so a session survives closing the shell or disconnecting from RDP. Reattach later with <code>tmux attach</code>.</p>
<h2 id="step-7-let-claude-code-use-a-logged-in-browser"><a class="anchor" href="#step-7-let-claude-code-use-a-logged-in-browser" aria-hidden="true" tabindex="-1">#</a>Step 7: Let Claude Code use a logged-in browser</h2>
<p>This is the main reason I built isolde. Many tasks involve web portals that need a login, often with MFA, which an automated browser can&#39;t get through on its own. Instead, you log in yourself in a Chromium window, and Claude Code connects to that window.</p>
<ol>
<li><p>In a terminal on the desktop, start Chromium with a dedicated profile and a debugging port:</p>
<pre><code class="language-bash">chromium --user-data-dir=&quot;$HOME/.config/claude-browser&quot; --remote-debugging-port=9222
</code></pre>
</li>
<li><p>Log in to the portals you need in that window.</p>
</li>
<li><p>Give Claude Code browser tools through Playwright MCP. You only need to do this once per project:</p>
<pre><code class="language-bash">claude mcp add playwright -- npx @playwright/mcp@latest --cdp-endpoint http://localhost:9222
</code></pre>
</li>
<li><p>Start <code>claude</code> and ask it to work in the portal.</p>
</li>
</ol>
<p>Keep the window visible so you can follow along and handle a CAPTCHA or an expired session. Keep in mind that Claude Code can do anything you could do in those portals, and that page content can try to give it instructions. Leave permission prompts on, review anything that submits, pays or deletes, and close the window when you&#39;ve finished, because anything in the container can control the browser while the debugging port is open.</p>
<h2 id="step-8-stop-the-container"><a class="anchor" href="#step-8-stop-the-container" aria-hidden="true" tabindex="-1">#</a>Step 8: Stop the container</h2>
<p>From the host, find the container with <code>docker ps</code> and stop it:</p>
<pre><code class="language-bash">docker stop isolde-foo-&lt;hash&gt;
</code></pre>
<p>Logging out of XFCE ends only the desktop session, and the container keeps running.</p>
<h2 id="what-persists-and-what-doesnt"><a class="anchor" href="#what-persists-and-what-doesnt" aria-hidden="true" tabindex="-1">#</a>What persists and what doesn&#39;t</h2>
<p>Containers are removed when they stop, so only two locations survive:</p>
<div class="table-wrap"><table>
<thead>
<tr>
<th>Location</th>
<th>Stored in</th>
<th>Kept</th>
</tr>
</thead>
<tbody><tr>
<td><code>/workspace</code></td>
<td>Your project directory on the host</td>
<td>Always</td>
</tr>
<tr>
<td><code>/home/dev</code></td>
<td>A Docker volume for that directory</td>
<td>Until you delete the volume</td>
</tr>
<tr>
<td>Everything else</td>
<td>The container</td>
<td>Lost when the container stops</td>
</tr>
</tbody></table></div>
<p>This means:</p>
<ul>
<li><strong>Install packages in the image:</strong> anything you install with <code>apt</code> at runtime is gone after a restart. Add it to the <code>Dockerfile</code> instead.</li>
<li><strong>Homes follow the path:</strong> renaming or moving a project directory gives it a new, empty home. The old volume stays until you delete it.</li>
</ul>
<p>The README explains how to list and delete homes, update Claude Code, and connect from another machine.</p>
<h2 id="a-note-on-security"><a class="anchor" href="#a-note-on-security" aria-hidden="true" tabindex="-1">#</a>A note on security</h2>
<p>isolde keeps projects apart from each other, but it isn&#39;t a strong security boundary. Anything running in the container, including Claude Code, can change the mounted project and has full network access. See the Security section of the README before using it with anything sensitive.</p>
<h2 id="try-it"><a class="anchor" href="#try-it" aria-hidden="true" tabindex="-1">#</a>Try it</h2>
<p>isolde is open source under the Apache-2.0 license: <a href="https://github.com/dmitrymatveyev/isolde">github.com/dmitrymatveyev/isolde</a>. If you try it, especially on macOS, Windows or an ARM machine, I&#39;d like to hear how it went. Issues and suggestions are welcome.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
