<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>SSH - Tag - Daily Deep Think</title>
        <link>https://blog.baifan.site/en/tags/ssh/</link>
        <description>SSH - Tag - Daily Deep Think</description>
        <generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>blog@baifan.site (ByF)</managingEditor>
            <webMaster>blog@baifan.site (ByF)</webMaster><lastBuildDate>Tue, 21 Apr 2026 14:00:00 &#43;0800</lastBuildDate><atom:link href="https://blog.baifan.site/en/tags/ssh/" rel="self" type="application/rss+xml" /><item>
    <title>All the Tmux You&#39;ll Ever Use: Sessions, Panes, Detach</title>
    <link>https://blog.baifan.site/en/tmux-practical-guide/</link>
    <pubDate>Tue, 21 Apr 2026 14:00:00 &#43;0800</pubDate><author>
                    <name>ByF</name>
                </author><guid>https://blog.baifan.site/en/tmux-practical-guide/</guid>
    <description><![CDATA[<div class="featured-image">
                <img src="/pictures/posts/tmux-session-window-pane.svg" referrerpolicy="no-referrer">
            </div><p>You SSH into a server to run a long task, the network drops, and the task is gone. Tmux exists to solve exactly this — it decouples the terminal session from the window, so the process keeps running after you close the terminal.</p>
<!-- more -->
<figure class="center"><a class="lightgallery" href="/pictures/posts/tmux-session-window-pane.svg" title="Tmux&#39;s three layers" data-thumbnail="/pictures/posts/tmux-session-window-pane.svg" data-sub-html="<h2>Tmux&rsquo;s three layers: a Session contains Windows, a Window contains Panes</h2><p>Tmux&#39;s three layers</p>"><img  loading="lazy" src='/pictures/posts/tmux-session-window-pane.svg'   alt="Tmux session-window-pane structure diagram"  width="800"></a><figcaption class="image-caption">Tmux&rsquo;s three layers: a Session contains Windows, a Window contains Panes</figcaption>
    </figure>
<h2 id="the-core-problem-it-solves" class="headerLink">
    <a href="#the-core-problem-it-solves" class="header-mark"></a>The Core Problem It Solves</h2><p>An ordinary terminal window is bound to its processes. Close the window and the processes die. Same story when SSH drops.</p>]]></description>
</item>
<item>
    <title>A Guide to SSH Remote Development in the Codex App</title>
    <link>https://blog.baifan.site/en/codex-ssh-remote-development-guide/</link>
    <pubDate>Tue, 10 Feb 2026 14:00:00 &#43;0800</pubDate><author>
                    <name>ByF</name>
                </author><guid>https://blog.baifan.site/en/codex-ssh-remote-development-guide/</guid>
    <description><![CDATA[<div class="featured-image">
                <img src="/pictures/note/codex-ssh-remote-featured.svg" referrerpolicy="no-referrer">
            </div><!-- more -->
<blockquote>
  <p><strong>Update note</strong>: This post is based on the Codex App as of May 2026. SSH Remote is still in alpha, and the configuration methods and UI entry points may change with new releases. If anything here has gone stale, refer to the <a href="https://github.com/openai/codex" target="_blank" rel="noopener noreferrer">official documentation</a> for the latest.</p>

</blockquote><p>The Codex App now supports connecting to remote machines over SSH; the feature is currently in alpha.</p>
<p>If you develop on remote servers, train models, or run environments there, this is worth a try. It lets you connect to a remote server directly inside Codex and work in the remote filesystem and shell — no more jumping back and forth between a local terminal, VSCode Remote, SSH, and tmux.</p>]]></description>
</item>
</channel>
</rss>
