Why Another tmux Post

You already know tmux is useful. We covered that. Sessions survive SSH drops. Panes let you monitor multiple things at once. The prefix-key workflow becomes muscle memory.

But knowing and doing are different things. Most tmux tutorials end after "here's how to split a pane." You try it once, forget the keybindings, and go back to opening five terminals.

The gap isn't knowledge — it's practice.

The fix is repetition. Not reading more blog posts. Not watching someone else do it on YouTube. You need to type the commands, hit the wrong keybinding, recover, and do it again until it's automatic.

That's what this challenge delivers.

What the Challenge Is

tmux 30-Day Zero-to-Hero is a structured, hands-on drill plan. Thirty days. Two to three hours daily. Each day builds on the last.

It runs at tmux.sandbox99.cc — an interactive site that tracks your progress. Create an account and your state saves across devices. Skip the account and it's browser-local storage only.

This isn't a read-and-forget guide. Every day has tasks. You execute them. You build muscle memory.

The Four Weeks

Week Focus What You'll Own by Friday
1 Core Concepts Sessions, windows, panes, copy mode — the fundamentals
2 Configuration .tmux.conf, layouts, status bar, keybindings
3 Scripting & Automation CLI scripting, tmuxp YAML sessions, SSH workflows
4 Plugins & Mastery TPM, resurrect, vim-tmux-navigator, production workflows

Each week ends with a review day. Week 4 ends with "The Gauntlet" — a final challenge that tests everything.

Week by Week

Week 1: Core Concepts

Days 1–7. You start from zero and build the foundation.

  • Day 1 — Client-server model. Your first session.
  • Days 2–3 — Windows and panes. Split, navigate, manage.
  • Day 4 — Combine windows and panes. Multi-view layouts.
  • Day 5 — Copy mode and scrolling. Navigate output without a mouse.
  • Day 6 — Session mastery. Name, switch, detach, reattach.
  • Day 7 — Week 1 review. Reinforce everything.

Week 2: Configuration & Layouts

Days 8–14. Make tmux yours.

  • Day 8 — Write your first .tmux.conf.
  • Days 9–10 — Layouts and status bar customization.
  • Days 11–12 — Keybindings, custom commands, command mode.
  • Day 13 — Colors, mouse support, UX polish.
  • Day 14 — Week 2 review. Build a config from scratch.

Week 3: Scripting & Automation

Days 15–21. Stop repeating yourself.

  • Days 15–16 — tmux CLI scripting. Idempotent session scripts.
  • Day 17 — tmuxp. Define sessions in YAML.
  • Day 18 — Shell integration. Auto-start, smart naming.
  • Days 19–20 — Pane synchronization. SSH + tmux remote workflow.
  • Day 21 — Week 3 review. Build an automation portfolio.

Week 4: Plugins & Mastery

Days 22–30. Production-grade workflows.

  • Days 22–24 — TPM, resurrect, continuum, vim-tmux-navigator.
  • Days 25–27 — Advanced features. Dev and sysadmin workflow design.
  • Day 28 — Nested tmux. Deep remote work patterns.
  • Day 29 — Performance and polish.
  • Day 30 — The Gauntlet. Final challenge.

How to Succeed

The structure works if you show up. A few tips from the design:

  • Daily blocks are 2–3 hours. Not a quick read. You sit down, open a terminal, and execute.
  • Each day builds on the last. Skip a day and the next one feels harder. Consistency beats cramming.
  • Week reviews matter. Days 7, 14, 21, and 30 are consolidation days. Don't skip them.
  • Create an account. Progress saves server-side. Lose your browser, lose your streak.
  • Use a real server if possible. The challenge works on any machine, but practicing on a VPS you actually manage makes the skills stick faster.

Who This Is For

  • Linux admins who use tmux but never went beyond basics
  • DevOps engineers who want scripted, reproducible workspaces
  • Self-hosters running VPS instances who need persistent monitoring
  • Anyone who read a tmux tutorial and forgot it two days later

If you already config your own .tmux.conf and script sessions, weeks 1–2 may be review. Start at Day 15.

 

Start Day 1

Go to tmux.sandbox99.cc. Creating an account is totally optional! If you're sticking to one device, your progress will be saved right there in the same device and browser — no sign-up needed. Ready when you are, go ahead and start the challenge!

Thirty days. Two hours daily. By Day 30, tmux isn't something you "know about" — it's something you use without thinking.