<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Remote-Development on Gert's blog</title><link>https://gertalot.com/tags/remote-development/</link><description>Recent content in Remote-Development on Gert's blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 17 Nov 2026 01:05:34 +0000</lastBuildDate><atom:link href="https://gertalot.com/tags/remote-development/index.xml" rel="self" type="application/rss+xml"/><item><title>Pasting images into remote Codex sessions</title><link>https://gertalot.com/posts/pasting-images-into-remote-codex-sessions/</link><pubDate>Tue, 17 Nov 2026 01:05:34 +0000</pubDate><guid>https://gertalot.com/posts/pasting-images-into-remote-codex-sessions/</guid><description>&lt;p&gt;My earlier post &lt;a href="https://gertalot.com/posts/seamless-remote-coding-sessions/"&gt;Seamless remote coding sessions&lt;/a&gt; shows how I use Tailscale,
Eternal Terminal and tmux to work on a Linux machine at home from my MacBook. The remote sessions appear as
regular iTerm2 panes, and reconnect when my network comes back.&lt;/p&gt;
&lt;p&gt;Often, I screenshot a window or area on my laptop to instruct codex. With local sessions, pasting the image into codex shows a text like &lt;code&gt;[Image #1]&lt;/code&gt; in the codex prompt input, and gives codex access to the image. With remote sessions this doesn&amp;rsquo;t work out-of-the-box: The screenshots will be stored in a tmp file locally that remote codex can&amp;rsquo;t access.&lt;/p&gt;</description></item></channel></rss>