{ "@context": "https://schema.org", "@id": "https://aggr.aymericbeaumet.com/items/steipete-me/2025-06-05-commanding-your-claude-code-army/#webpage", "@type": [ "WebPage", "ArchiveComponent" ], "articleBody": "![](https://steipete.me/assets/img/2025/commanding-your-claude-code-army/header.png)\n\n> **Update**: There’s a better solution now! Check out [Command Your Claude Code Army, Reloaded](https://steipete.me/posts/2025/command-your-claude-code-army-reloaded/) for VibeTunnel integration that gives Claude automatic title management.\n\n**TL;DR**: Running multiple Claude Code instances? Here’s a ZSH trick to keep your terminal titles organized and your sanity intact.\n\nI’ll admit it - I’ve become a [Claude Code](https://www.anthropic.com/claude-code) power user. At any given moment, I have at least three instances running: one for writing blog posts, another fixing that “quick” bug that’s now in hour three, and a third doing something I definitely forgot about. My terminal looks like a Claude Code convention.\n\n## The Problem: Too Many Claudes, Not Enough Context\n\n[Ghostty](https://ghostty.org/) (yes, with two T’s - it’s my favorite terminal) only shows the process name in the title. When you have six tabs all saying “claude”, finding the right one becomes a game of terminal roulette.\n\nThis is especially painful when you’re running Claude with the `--dangerously-skip-permissions` flag (yes, I live dangerously - see my post about [Claude Code being my computer](https://steipete.me/posts/2025/claude-code-is-my-computer/)). The last thing you want is to accidentally run the wrong command in the wrong directory with full system permissions.\n\nTo make matters worse, Claude Code has a habit of changing the terminal title to whatever it feels like - usually something unhelpful like “Running command…” or just “claude”. It’s like having a helpful assistant who keeps reorganizing your desk while you’re trying to work.\n\n## The Solution: Terminal Title Magic\n\nHere’s my approach - a clean ZSH setup that keeps terminal management code separate from my main configuration. First, I add one line to my `~/.zshrc`:\n\n```zsh\n# Source Claude wrapper with dynamic terminal title\n[ -f ~/.config/zsh/claude-wrapper.zsh ] && source ~/.config/zsh/claude-wrapper.zsh\n```\n\nThen I create `~/.config/zsh/claude-wrapper.zsh` with the actual implementation:\n\n```zsh\n#!/usr/bin/env zsh\n# Simple, elegant terminal title management for Claude\n\n# Set terminal title\n_set_title() { \n print -Pn \"\\e]2;$1\\a\" \n}\n\n# Claude wrapper with custom terminal title\ncly() {\n local folder=${PWD:t} # Just the current folder name\n \n # Set title to show we're running Claude\n _set_title \"$folder — Claude\"\n \n # Start a background process to continuously reset the title\n # (prevents Claude from changing it)\n (\n while true; do\n _set_title \"$folder — Claude\"\n sleep 0.5\n done\n ) &\n local title_pid=$!\n \n # Run Claude with dangerous permissions\n \"$HOME/.claude/local/claude\" --dangerously-skip-permissions \"$@\"\n local exit_code=$?\n \n # Kill the background title setter\n kill $title_pid 2>/dev/null\n wait $title_pid 2>/dev/null # Clean up zombie process\n \n # Restore normal title\n _set_title \"%~\"\n \n # Return the original exit code\n return $exit_code\n}\n\n# Update terminal title before each prompt (using proper ZSH hooks)\n_claude_precmd() {\n _set_title \"%~\"\n}\n\n# Add our precmd function to the array (doesn't overwrite existing hooks)\nif [[ -z ${precmd_functions[(r)_claude_precmd]} ]]; then\n precmd_functions+=(_claude_precmd)\nfi\n```\n\nWhen I run `cly`, my terminal title changes from `~/Projects/blog` to `~/Projects/blog — Claude`. Revolutionary? No. Life-changing? Absolutely.\n\n> *Hot tip: Just ask Claude to read this blog post and set it up for you! (in yolo mode, of course)*\n\nNow if you’ll excuse me, I need to check on my Claude instances. I think one of them is refactoring my entire codebase without asking. Again.\n", "authors": [], "captured_at": "2026-09-27T19:29:15.293681927+00:00", "category": "programming", "content_html": "

\"\"

\n
\n

Update: There’s a better solution now! Check out Command Your Claude Code Army, Reloaded for VibeTunnel integration that gives Claude automatic title management.

\n
\n

TL;DR: Running multiple Claude Code instances? Here’s a ZSH trick to keep your terminal titles organized and your sanity intact.

\n

I’ll admit it - I’ve become a Claude Code power user. At any given moment, I have at least three instances running: one for writing blog posts, another fixing that “quick” bug that’s now in hour three, and a third doing something I definitely forgot about. My terminal looks like a Claude Code convention.

\n

The Problem: Too Many Claudes, Not Enough Context

\n

Ghostty (yes, with two T’s - it’s my favorite terminal) only shows the process name in the title. When you have six tabs all saying “claude”, finding the right one becomes a game of terminal roulette.

\n

This is especially painful when you’re running Claude with the --dangerously-skip-permissions flag (yes, I live dangerously - see my post about Claude Code being my computer). The last thing you want is to accidentally run the wrong command in the wrong directory with full system permissions.

\n

To make matters worse, Claude Code has a habit of changing the terminal title to whatever it feels like - usually something unhelpful like “Running command…” or just “claude”. It’s like having a helpful assistant who keeps reorganizing your desk while you’re trying to work.

\n

The Solution: Terminal Title Magic

\n

Here’s my approach - a clean ZSH setup that keeps terminal management code separate from my main configuration. First, I add one line to my ~/.zshrc:

\n
# Source Claude wrapper with dynamic terminal title\n[ -f ~/.config/zsh/claude-wrapper.zsh ] && source ~/.config/zsh/claude-wrapper.zsh\n
\n

Then I create ~/.config/zsh/claude-wrapper.zsh with the actual implementation:

\n
#!/usr/bin/env zsh\n# Simple, elegant terminal title management for Claude\n\n# Set terminal title\n_set_title() { \n    print -Pn "\\e]2;$1\\a" \n}\n\n# Claude wrapper with custom terminal title\ncly() {\n    local folder=${PWD:t}  # Just the current folder name\n    \n    # Set title to show we're running Claude\n    _set_title "$folder — Claude"\n    \n    # Start a background process to continuously reset the title\n    # (prevents Claude from changing it)\n    (\n        while true; do\n            _set_title "$folder — Claude"\n            sleep 0.5\n        done\n    ) &\n    local title_pid=$!\n    \n    # Run Claude with dangerous permissions\n    "$HOME/.claude/local/claude" --dangerously-skip-permissions "$@"\n    local exit_code=$?\n    \n    # Kill the background title setter\n    kill $title_pid 2>/dev/null\n    wait $title_pid 2>/dev/null  # Clean up zombie process\n    \n    # Restore normal title\n    _set_title "%~"\n    \n    # Return the original exit code\n    return $exit_code\n}\n\n# Update terminal title before each prompt (using proper ZSH hooks)\n_claude_precmd() {\n    _set_title "%~"\n}\n\n# Add our precmd function to the array (doesn't overwrite existing hooks)\nif [[ -z ${precmd_functions[(r)_claude_precmd]} ]]; then\n    precmd_functions+=(_claude_precmd)\nfi\n
\n

When I run cly, my terminal title changes from ~/Projects/blog to ~/Projects/blog — Claude. Revolutionary? No. Life-changing? Absolutely.

\n
\n

Hot tip: Just ask Claude to read this blog post and set it up for you! (in yolo mode, of course)

\n
\n

Now if you’ll excuse me, I need to check on my Claude instances. I think one of them is refactoring my entire codebase without asking. Again.

\n", "content_markdown": "![](https://steipete.me/assets/img/2025/commanding-your-claude-code-army/header.png)\n\n> **Update**: There’s a better solution now! Check out [Command Your Claude Code Army, Reloaded](https://steipete.me/posts/2025/command-your-claude-code-army-reloaded/) for VibeTunnel integration that gives Claude automatic title management.\n\n**TL;DR**: Running multiple Claude Code instances? Here’s a ZSH trick to keep your terminal titles organized and your sanity intact.\n\nI’ll admit it - I’ve become a [Claude Code](https://www.anthropic.com/claude-code) power user. At any given moment, I have at least three instances running: one for writing blog posts, another fixing that “quick” bug that’s now in hour three, and a third doing something I definitely forgot about. My terminal looks like a Claude Code convention.\n\n## The Problem: Too Many Claudes, Not Enough Context\n\n[Ghostty](https://ghostty.org/) (yes, with two T’s - it’s my favorite terminal) only shows the process name in the title. When you have six tabs all saying “claude”, finding the right one becomes a game of terminal roulette.\n\nThis is especially painful when you’re running Claude with the `--dangerously-skip-permissions` flag (yes, I live dangerously - see my post about [Claude Code being my computer](https://steipete.me/posts/2025/claude-code-is-my-computer/)). The last thing you want is to accidentally run the wrong command in the wrong directory with full system permissions.\n\nTo make matters worse, Claude Code has a habit of changing the terminal title to whatever it feels like - usually something unhelpful like “Running command…” or just “claude”. It’s like having a helpful assistant who keeps reorganizing your desk while you’re trying to work.\n\n## The Solution: Terminal Title Magic\n\nHere’s my approach - a clean ZSH setup that keeps terminal management code separate from my main configuration. First, I add one line to my `~/.zshrc`:\n\n```zsh\n# Source Claude wrapper with dynamic terminal title\n[ -f ~/.config/zsh/claude-wrapper.zsh ] && source ~/.config/zsh/claude-wrapper.zsh\n```\n\nThen I create `~/.config/zsh/claude-wrapper.zsh` with the actual implementation:\n\n```zsh\n#!/usr/bin/env zsh\n# Simple, elegant terminal title management for Claude\n\n# Set terminal title\n_set_title() { \n print -Pn \"\\e]2;$1\\a\" \n}\n\n# Claude wrapper with custom terminal title\ncly() {\n local folder=${PWD:t} # Just the current folder name\n \n # Set title to show we're running Claude\n _set_title \"$folder — Claude\"\n \n # Start a background process to continuously reset the title\n # (prevents Claude from changing it)\n (\n while true; do\n _set_title \"$folder — Claude\"\n sleep 0.5\n done\n ) &\n local title_pid=$!\n \n # Run Claude with dangerous permissions\n \"$HOME/.claude/local/claude\" --dangerously-skip-permissions \"$@\"\n local exit_code=$?\n \n # Kill the background title setter\n kill $title_pid 2>/dev/null\n wait $title_pid 2>/dev/null # Clean up zombie process\n \n # Restore normal title\n _set_title \"%~\"\n \n # Return the original exit code\n return $exit_code\n}\n\n# Update terminal title before each prompt (using proper ZSH hooks)\n_claude_precmd() {\n _set_title \"%~\"\n}\n\n# Add our precmd function to the array (doesn't overwrite existing hooks)\nif [[ -z ${precmd_functions[(r)_claude_precmd]} ]]; then\n precmd_functions+=(_claude_precmd)\nfi\n```\n\nWhen I run `cly`, my terminal title changes from `~/Projects/blog` to `~/Projects/blog — Claude`. Revolutionary? No. Life-changing? Absolutely.\n\n> *Hot tip: Just ask Claude to read this blog post and set it up for you! (in yolo mode, of course)*\n\nNow if you’ll excuse me, I need to check on my Claude instances. I think one of them is refactoring my entire codebase without asking. Again.\n", "dateCreated": "2026-09-27T19:29:15.293681927+00:00", "date_created": "2025-06-05T09:00:00+00:00", "date_modified": "2025-06-05T09:00:00+00:00", "date_published": "2025-06-05T09:00:00+00:00", "description": "How a simple terminal trick helps me manage multiple Claude Code instances without losing my mind (or my terminal tabs)", "external_url": "https://steipete.me/posts/2025/commanding-your-claude-code-army/", "git": { "commit": "ebb0941c5c06a2ab2377342d607535262a3e969e", "path": "items/steipete-me/2025/06/2025-06-05-commanding-your-claude-code-army.md", "permalink": "https://github.com/aymericbeaumet/aggr-instance/blob/ebb0941c5c06a2ab2377342d607535262a3e969e/items/steipete-me/2025/06/2025-06-05-commanding-your-claude-code-army.md" }, "id": "urn:aggr:item:6b88db97dacb072f477af994b3ee27864767b0a2", "isBasedOn": { "@id": "https://steipete.me/posts/2025/commanding-your-claude-code-army/" }, "mainEntity": { "@id": "https://steipete.me/posts/2025/commanding-your-claude-code-army/", "@type": "CreativeWork", "archivedAt": { "@id": "https://aggr.aymericbeaumet.com/items/steipete-me/2025-06-05-commanding-your-claude-code-army/#webpage" }, "dateModified": "2025-06-05T09:00:00+00:00", "datePublished": "2025-06-05T09:00:00+00:00", "headline": "Commanding Your Claude Code Army", "timeRequired": "PT3M", "url": "https://steipete.me/posts/2025/commanding-your-claude-code-army/", "wordCount": 503 }, "name": "Archived snapshot: Commanding Your Claude Code Army", "preview": null, "reading_minutes": 3, "replicated_at": null, "source": "steipete-me", "source_name": "Peter Steinberger", "summary": "How a simple terminal trick helps me manage multiple Claude Code instances without losing my mind (or my terminal tabs)", "tags": [], "temporalCoverage": "2026-09-27T19:29:15.293681927+00:00", "title": "Commanding Your Claude Code Army", "url": "https://aggr.aymericbeaumet.com/items/steipete-me/2025-06-05-commanding-your-claude-code-army/", "word_count": 503 }