tmux for persistent sessions in Linux CLI - Step-by-Step Execution

Concept Flow - tmux for persistent sessions

Start tmux session

↓

Run commands inside tmux

↓

Detach session (leave running)

↓

Logout or close terminal

↓

Reattach to tmux session later

↓

Continue work where left off

This flow shows how tmux starts a session, lets you run commands, detach safely, and reattach later to keep your work persistent.

Execution Sample

Linux CLI

tmux new -s mysession
# Run commands inside tmux
# Detach with Ctrl+b d

tmux attach -t mysession

Starts a tmux session named 'mysession', lets you detach and reattach to keep your session alive.

Execution Table

Step	Command Entered	Action Taken	Session State	Output/Result
1	tmux new -s mysession	Create new tmux session named 'mysession'	Session 'mysession' active	New shell prompt inside tmux
2	# Run commands	User runs commands inside tmux	Session 'mysession' active	Command outputs shown inside tmux
3	Ctrl+b d	Detach from tmux session	Session 'mysession' running in background	Returns to normal shell prompt
4	logout or close terminal	Terminal closed, tmux session persists	Session 'mysession' still running	No output, session alive
5	tmux attach -t mysession	Reattach to existing session	Session 'mysession' active	Shell prompt inside tmux with previous state
6	exit	Exit tmux session	Session 'mysession' terminated	tmux session ends, back to normal shell

💡 Session ends when user types 'exit' inside tmux or kills the session explicitly

Variable Tracker

Variable	Start	After Step 1	After Step 3	After Step 5	Final
tmux session state	none	active	detached (running)	attached (active)	terminated

Key Moments - 3 Insights

Why does the tmux session keep running after I close the terminal?

Because at Step 3 you detached the session (Ctrl+b d), tmux keeps it running in the background even if the terminal closes, as shown in the execution_table row 4.

What happens if I don't detach and just close the terminal?

If you close the terminal without detaching, the tmux session usually ends. Detaching (Step 3) is necessary to keep the session persistent, as shown in the execution_table.

How do I get back to my work after detaching?

You use 'tmux attach -t mysession' (Step 5) to reattach and continue exactly where you left off, as shown in the execution_table.

Visual Quiz - 3 Questions

Look at the execution table, what is the tmux session state right after detaching with Ctrl+b d?

A Session terminated

B Session running in background (detached)

C Session active and attached

D No session exists

💡 Hint

Check Step 3 and Step 4 in the execution_table under 'Session State'

At which step does the user reattach to the tmux session?

A Step 2

B Step 3

C Step 5

D Step 6

💡 Hint

Look for the command 'tmux attach -t mysession' in the execution_table

If the user never detaches and closes the terminal, what likely happens to the tmux session?

A Session terminates when terminal closes

B Session automatically reattaches

C Session stays running in background

D Session duplicates

💡 Hint

Refer to key_moments about detaching necessity and execution_table explanation

Concept Snapshot

tmux lets you create persistent terminal sessions.
Use 'tmux new -s name' to start.
Detach anytime with Ctrl+b d to keep session alive.
Reattach with 'tmux attach -t name' to continue.
Sessions persist even if terminal closes.
Exit session with 'exit' inside tmux.

Full Transcript

This visual execution shows how tmux creates a persistent session. First, you start a session with 'tmux new -s mysession'. Inside, you run commands as usual. When ready, detach with Ctrl+b d to leave the session running in the background. You can safely close your terminal; the session stays alive. Later, reattach with 'tmux attach -t mysession' to continue your work exactly where you left off. Finally, exit the session with 'exit' to end it. This process helps keep your work safe and persistent across logouts or disconnections.