{"id":644,"date":"2026-08-13T22:39:22","date_gmt":"2026-08-13T19:39:22","guid":{"rendered":"https:\/\/ahaddad-wp.duckdns.org\/my\/mylogbook\/?post_type=doc_article&p=644"},"modified":"2026-08-13T23:48:41","modified_gmt":"2026-08-13T20:48:41","slug":"claude-in-powershell-and-tmux","status":"publish","type":"doc_article","link":"https:\/\/ahaddad-wp.duckdns.org\/my\/mylogbook\/docs\/claude-in-powershell-and-tmux\/","title":{"rendered":"Claude in Powershell and tmux"},"content":{"rendered":"\n
    \n
  1. Open PowerShell (or WSL) and SSH in the same way as always:
    ssh ahmad@100.111.255.36<\/li>\n\n\n\n
  2. Once connected, resume this exact conversation:
    claude –continue<\/li>\n\n\n\n
  3. That picks up the most recent conversation automatically \u2014 including all the context from this whole session. If for some reason it doesn’t grab the right one, claude –resume (no argument) shows a picker of recent sessions to choose from.<\/li>\n<\/ol>\n\n\n\n

    Worth mentioning for later, not right now: since this session isn’t in tmux, any future SSH hiccup (not just this lid test) would kill it the same way \u2014 running long Claude Code sessions inside tmux makes them survive disconnects entirely, so you could reconnect without even needing –continue. I won’t set that up mid-session since it’d mean restarting this one, but it’s worth doing next time you start a fresh session.<\/p>\n\n\n\n

    tmux<\/h2>\n\n\n\n

    The concept: normally, when you SSH in and run a command, that command lives inside your SSH connection \u2014 close the connection, and the command dies with it. tmux creates a persistent “terminal session” that lives on the server itself, independent of any SSH connection. You can “detach” from it (leave it running, disconnect), then “reattach” later from anywhere \u2014 even a different device \u2014 and it’s exactly as you left it.<\/p>\n\n\n\n

    Starting a fresh session (do this instead of just typing claude directly next time):
    tmux new -s claude
    -s claude names it “claude” so it’s easy to find later. You’re now inside a normal-looking terminal \u2014 run claude here as usual.<\/p>\n\n\n\n

    Detaching (leave it running, safe to close your laptop\/lose connection):
    Press Ctrl+b, release, then press d. You’ll drop back to your regular shell, and the session keeps running in the background on the server.<\/p>\n\n\n\n

    Reattaching later (from any device, any time):
    tmux attach -t claude
    You’re back exactly where you left off \u2014 full scrollback, Claude Code mid-conversation, everything intact.<\/p>\n\n\n\n

    Other useful commands:
    tmux ls # list all running sessions
    tmux kill-session -t claude # end it permanently when you’re really done<\/p>\n\n\n\n

    That’s genuinely most of what you need day-to-day. The one habit to build: whenever you’re about to start something long-running (a Claude Code session, a big transfer), do it inside tmux new -s first, so a dropped connection never costs you the session.<\/p>\n\n\n\n

    Installing tmux<\/h2>\n\n\n\n

    aThere wasn’t a separate “setup” step beyond what’s already true \u2014 tmux was already installed on the server (we added it earlier during the media transfer). The “setup” is really just the workflow itself. Here’s the clean version for your notes:<\/p>\n\n\n\n

    Check it’s installed (already is, on this server):
    which tmux<\/p>\n\n\n\n

    Start a new named session (do this instead of running claude directly):
    tmux new -s claude<\/p>\n\n\n\n

    Detach (leaves it running, safe to disconnect): press Ctrl+b, release, then d<\/p>\n\n\n\n

    Reattach later (from any device, any time):
    tmux attach -t claude<\/p>\n\n\n\n

    List running sessions:
    tmux ls<\/p>\n\n\n\n

    End a session permanently:
    tmux kill-session -t claude<\/p>\n\n\n\n

    That’s the complete setup \u2014 no config file, no service, nothing else to install. The one habit worth documenting: start any long-running SSH work (a Claude Code session, a big file transfer) inside tmux new -s first, so a dropped connection never costs you the session.<\/p>\n\n\n\n

    <\/p>\n","protected":false},"excerpt":{"rendered":"

    Worth mentioning for later, not right now: since this session isn’t in tmux, any future SSH hiccup (not just this lid test) would kill it the same way \u2014 running long Claude Code sessions inside tmux makes them survive disconnects entirely, so you could reconnect without even needing –continue. I won’t set that up mid-session […]<\/p>\n","protected":false},"featured_media":646,"template":"","project_category":[123,152],"class_list":["post-644","doc_article","type-doc_article","status-publish","has-post-thumbnail","hentry","project_category-docs","project_category-guides"],"_links":{"self":[{"href":"https:\/\/ahaddad-wp.duckdns.org\/my\/mylogbook\/wp-json\/wp\/v2\/doc_article\/644","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ahaddad-wp.duckdns.org\/my\/mylogbook\/wp-json\/wp\/v2\/doc_article"}],"about":[{"href":"https:\/\/ahaddad-wp.duckdns.org\/my\/mylogbook\/wp-json\/wp\/v2\/types\/doc_article"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ahaddad-wp.duckdns.org\/my\/mylogbook\/wp-json\/wp\/v2\/media\/646"}],"wp:attachment":[{"href":"https:\/\/ahaddad-wp.duckdns.org\/my\/mylogbook\/wp-json\/wp\/v2\/media?parent=644"}],"wp:term":[{"taxonomy":"project_category","embeddable":true,"href":"https:\/\/ahaddad-wp.duckdns.org\/my\/mylogbook\/wp-json\/wp\/v2\/project_category?post=644"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}