Claude Code Guides

Practical write-ups for two problems every Claude Code power user runs into: keeping several sessions running at once without them stepping on each other, and knowing the moment one of them actually needs you.

Running sessions in parallel

• Running Claude Code in Parallel with Git Worktrees

  One clone, one branch per session, zero collisions — the worktree setup we actually use.

• How to Manage Multiple Claude Code Sessions Without Losing Track

  Worktrees, tmux, and terminal layouts compared — and how to know instantly which session needs you.

• A Practical tmux Workflow for Claude Code

  Named windows per session, panes vs. windows, and surviving SSH disconnects.

Staying aware of what needs you

• How to Get Claude Code Notifications on macOS

  Native terminal notifications, the terminal bell, and hook-based alerts — copy-paste setup included.

• Tracking Claude Code Session Status with Hooks

  How to turn hook events into a reliable waiting / running / done state, edge cases included.

Hooks: tools and reference

• Claude Code Hooks Builder

  Tick the events, type one command, copy a settings.json that Claude Code accepts as-is. Free, no sign-up.

• Claude Code Hooks Reference

  All 33 hook events with matcher values, stdin fields, the settings and statusLine schema, exit codes, and the session state file.