Remote Claude Code Terminal Access: Check on Your AI Agent from Anywhere

For AI coding agents, that persistence is the whole point:

• Long-running tasks: Initiate a process, close your laptop, and return hours later to find it still active.
• Remote access: Reconnect to your session from any device, anywhere in the world.
• Collaboration: Multiple users can simultaneously view and interact with the same session.
• Organization: Assign each agent its own named session to maintain clarity.

To start using tmux, you'll need to install it on your system. Here's how to do it across different operating systems:

# Ubuntu / Debian / Pop!_OS
sudo apt install tmux

# macOS
brew install tmux

# Fedora / RHEL / Rocky
sudo dnf install tmux

# Arch
sudo pacman -S tmux

# Windows: Install WSL2 first, then run the Ubuntu command above

Verify it with tmux -V. On the Pop!_OS machine I tested this on, that printed tmux 3.4. Anything in the 3.x range behaves the same for everything below.

These five commands cover almost everything you'll do day to day. I ran tmux new-session -d -s claude followed by tmux ls on my own box and it listed the detached session immediately, alongside the other agent sessions already running there (cursor-agent, copilot-agent, and so on). That ls output is your proof the session survived.

# Create a named session
tmux new-session -s claude

# Detach from session (session keeps running)
# Press: Ctrl+B, then D

# List running sessions
tmux ls

# Re-attach to a session
tmux attach-session -t claude

# Switch between sessions (from inside tmux)
tmux switch-client -t cursor-agent

# Kill a session
tmux kill-session -t claude

Some terminal applications, like Warp, use tmux internally, which can lead to conflicts. If you encounter the error sessions should be nested with care, unset $TMUX to force, resolve it by clearing the TMUX variable:

TMUX= tmux new-session -s claude
TMUX= tmux attach-session -t claude

To streamline your workflow, create aliases for each AI agent session. Add these to your ~/.bashrc or ~/.zshrc:

# Claude Code
function cn {
  if tmux has-session -t claude 2>/dev/null; then
    tmux attach-session -t claude
  else
    tmux new-session -d -s claude -c ~/Projects/your-project
    tmux send-keys -t claude "claude --dangerously-skip-permissions" Enter
    tmux attach-session -t claude
  fi
}

# Cursor Agent
function cu {
  if tmux has-session -t cursor-agent 2>/dev/null; then
    tmux attach-session -t cursor-agent
  else
    tmux new-session -d -s cursor-agent -c ~/Projects/your-project
    tmux send-keys -t cursor-agent "cursor agent" Enter
    tmux attach-session -t cursor-agent
  fi
}

# Additional aliases for other agents...

Reload your shell configuration with source ~/.bashrc.

• tmux provides persistent terminal sessions, crucial for managing long-running AI tasks.
• Essential commands like creating, detaching, and re-attaching sessions are fundamental for effective use.
• Aliases can significantly streamline your workflow by simplifying session management.

Install ttyd using the following commands:

# Ubuntu / Debian
sudo apt install ttyd

# macOS
brew install ttyd

# Fedora
sudo dnf install ttyd

# Manual installation for other Linux distributions
sudo curl -L https://github.com/tsl0922/ttyd/releases/latest/download/ttyd.x86_64 \
  -o /usr/local/bin/ttyd && sudo chmod +x /usr/local/bin/ttyd

Verify with ttyd --version. Mine reported ttyd version 1.7.4.

To test ttyd, start it with your claude session:

# Start ttyd pointing at your claude session (port 7682)
ttyd -p 7682 tmux new-session -A -s claude

# Open http://localhost:7682 in your browser

You should see a terminal interface where you can interact with your tmux session.

To ensure your terminal is secure, never expose an unauthenticated terminal to the public internet. Use a two-port strategy:

• Port 7682: Loopback only, no authentication (for local admin panel).
• Port 7681: Authenticated and exposed via Cloudflare for remote access.

# Loopback only
ttyd --port 7682 --interface lo --writable tmux new-session -A -s claude

# Authenticated access
ttyd --port 7681 -c yourusername:your-password --writable tmux new-session -A -s claude

• ttyd allows browser-based terminal access, making remote management more accessible.
• Always secure your terminal access with authentication to prevent unauthorized access.

Cloudflare Tunnel gives your terminal a permanent public URL without opening a single port on your firewall. The tunnel dials out to Cloudflare, so there's nothing inbound to attack. Access control rides on your existing Cloudflare account. The cloudflared version I installed was 2026.5.0.

Install cloudflared using the following commands:

# macOS
brew install cloudflare/cloudflare/cloudflared

# Ubuntu / Debian
curl -L https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64.deb \
  -o cloudflared.deb && sudo dpkg -i cloudflared.deb

# Arch
sudo pacman -S cloudflared

# Windows (PowerShell)
winget install Cloudflare.cloudflared

Authenticate and create a tunnel:

# Authenticate (opens browser to Cloudflare login)
cloudflared tunnel login

# Create the tunnel
cloudflared tunnel create terminal

# Route your subdomain to this tunnel
cloudflared tunnel route dns terminal terminal.yourdomain.com

Configure the tunnel by creating a configuration file ~/.cloudflared/terminal-config.yml:

tunnel: YOUR-TUNNEL-UUID-HERE
credentials-file: /home/YOUR-USERNAME/.cloudflared/YOUR-TUNNEL-UUID.json

ingress:
  - hostname: terminal.yourdomain.com
    service: http://localhost:7681
    originRequest:
      noTLSVerify: true
      connectTimeout: 30s
  - service: http_status:404

Test your setup with:

cloudflared tunnel --config ~/.cloudflared/terminal-config.yml run terminal

• Cloudflare Tunnel provides a secure, always-on public URL for your terminal sessions.
• Proper configuration ensures seamless integration with your existing infrastructure.

To ensure your agent sessions start automatically, create systemd user services. Here's an example script for the claude session:

#!/bin/bash
export HOME=/home/YOUR-USERNAME
export PATH=/home/YOUR-USERNAME/.local/bin:/usr/local/bin:/usr/bin:/bin
export TERM=xterm-256color
export TMUX_TMPDIR=/tmp

tmux kill-session -t claude 2>/dev/null || true
tmux new-session -d -s claude -c /home/YOUR-USERNAME/Projects/your-project \; \
  send-keys "claude --dangerously-skip-permissions" Enter

Make the script executable:

chmod +x ~/.local/bin/start-claude-session.sh

Create similar scripts for other agents and configure them as systemd services to start on boot.

• Automating session management with systemd ensures your AI agents are always ready to go.
• Custom scripts can be tailored to fit the specific needs of each agent.

Three tools, one pipeline. tmux keeps the session alive, ttyd puts it in a browser, and Cloudflare Tunnel hands you a URL you can hit from a phone on the train. The piece people skip is the security step: keep the unauthenticated terminal on loopback, and only expose the password-protected port through the tunnel. Get that wrong and you've published a root shell to the internet. Get it right and you can babysit a long agent run from anywhere without an SSH key in sight.